All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)
Date: Wed, 23 Nov 2022 09:03:08 +0900	[thread overview]
Message-ID: <xmqqmt8ipmf7.fsf@gitster.g> (raw)
In-Reply-To: <Y3rDQ3x44BUmmGHV@nand.local> (Taylor Blau's message of "Sun, 20 Nov 2022 19:16:03 -0500")

Taylor Blau <me@ttaylorr.com> writes:

> These are the topics I'd feel comfortable merging down before the
> release candidate:
>
>  + pw/rebase-no-reflog-action                                   11-09/11-14    #2
>  + pw/strict-label-lookups                                      11-10/11-14    #2
>  + dd/bisect-helper-subcommand                                  11-11/11-14    #3
>  + js/remove-stale-scalar-repos                                 11-11/11-14    #2
>  + ab/coccicheck-incremental                                    11-11/11-14   #14
>  + kz/merge-tree-merge-base                                     11-12/11-14    #2
>  + ab/t7610-timeout                                             11-15/11-15    #2
>  + dd/git-bisect-builtin                                        11-15/11-15   #13
>  + rp/maintenance-qol                                           11-15/11-15    #4
>
> I also feel comfortable with these (below), but they are newer topics
> than above. I would like to see at least ps/receive-use-only-advertised
> in this release, since it saw the most comprehensive review of any of
> these.
>
>  + mh/gitcredentials-generate                                   11-14/11-18    #1
>  + jt/submodule-on-demand                                       11-14/11-18    #1
>  + ps/receive-use-only-advertised                               11-17/11-18    #7
>  + jk/parse-object-type-mismatch                                11-18/11-18    #2
>
> These ones I am not as sure about, though Ævar (cc'd) will probably try
> and tell you they're ready to go ;-).
>
>  + ab/cmake-nix-and-ci                                          11-04/11-08   #14
>  + ab/submodule-helper-prep-only                                11-08/11-08    #9
>
> Thanks,
> Taylor


Thanks.  After trying to catch up with the in-flight topics, I
mostly agree with the above list.

  reply	other threads:[~2022-11-23  0:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  2:22 What's cooking in git.git (Nov 2022, #04; Fri, 18) Taylor Blau
2022-11-20 11:24 ` SZEDER Gábor
2022-11-20 17:42 ` Looking for a review (pretty-formats, hard truncation), was What's cooking in git.git (Nov 2022, #04; Fri, 18)) Philip Oakley
2022-11-21  0:37   ` Junio C Hamano
2022-11-21 18:10     ` Philip Oakley
2022-11-20 19:46 ` What's cooking in git.git (Nov 2022, #04; Fri, 18) Phillip Wood
2022-11-20 21:24   ` Johannes Schindelin
2022-11-21  0:47     ` Junio C Hamano
2022-11-21  1:00       ` Taylor Blau
2022-11-22 14:58     ` Phillip Wood
2022-11-20 21:45 ` Junio C Hamano
2022-11-20 23:51   ` Taylor Blau
2022-11-20 23:24 ` Junio C Hamano
2022-11-20 23:52   ` Taylor Blau
2022-11-21  3:36     ` Junio C Hamano
2022-11-22 22:56       ` Taylor Blau
2022-11-21  0:10 ` Junio C Hamano
2022-11-21  0:16   ` Taylor Blau
2022-11-23  0:03     ` Junio C Hamano [this message]
2022-11-21 22:22 ` ab/submodule-no-abspath (was Re: What's cooking in git.git (Nov 2022, #04; Fri, 18)) Glen Choo
2022-11-22 22:45   ` [PATCH] submodule absorbgitdirs: use relative <from> and <to> paths Ævar Arnfjörð Bjarmason
2022-11-23  0:43     ` Glen Choo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqmt8ipmf7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.