git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Preparing to rewind 'next'
Date: Tue, 20 Oct 2020 12:17:15 -0700	[thread overview]
Message-ID: <xmqqtuuobtc4.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqr1put77h.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Mon, 19 Oct 2020 11:13:22 -0700")

Now 2.29 is out, it's time to clean the desk and to prepare for the
next cycle.  Typically a week after a release, we rebuild the tip of
'next' and it is an opportunity to kick some topics out of 'next'.

Here are the topics that are in next and have been marked as "Will
cook in 'next'" during the pre-release freeze period.  

Please nominate topics that should be kicked out of 'next', either
tentatively to give them a fresh chance to apply minor clean-ups (or
permanently because they are fundamentally wrong---but hopefully
there is no topic in the latter category).

Thanks.

 + ds/maintenance-part-2                                        09-25/10-04    #8
 + sk/force-if-includes                                         10-03/10-04    #4
 + mt/parallel-checkout-part-1                                  10-05/10-05   #20
 + sb/clone-origin                                              09-30/10-06    #7
 + jk/symlinked-dotgitx-files                                   10-06/10-08    #8
 + dl/checkout-p-merge-base                                     10-07/10-08    #4
 + js/userdiff-php                                              10-07/10-08    #1
 + kb/userdiff-rust-macro-rules                                 10-07/10-08    #1
 + rk/completion-stash                                          10-07/10-08    #2
 + dl/checkout-guess                                            10-08/10-08    #2
 + sd/userdiff-css-update                                       10-08/10-08    #1
 + cw/ci-ghwf-check-ws-errors                                   10-09/10-15    #1
 + rs/dist-doc-with-git-archive                                 10-12/10-15    #2
 + rs/tighten-callers-of-deref-tag                              10-12/10-15    #3
 + rs/worktree-list-show-locked                                 10-12/10-15    #1

  parent reply	other threads:[~2020-10-20 19:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 18:13 What's cooking in git.git (Oct 2020, #03; Mon, 19) Junio C Hamano
2020-10-19 18:21 ` Eric Sunshine
2020-10-20 22:59   ` Junio C Hamano
2020-10-20 19:17 ` Junio C Hamano [this message]
2020-10-20 19:37   ` Preparing to rewind 'next' Matheus Tavares Bernardino
2020-10-21 14:48 ` mr/bisect-in-c-3, was Re: What's cooking in git.git (Oct 2020, #03; Mon, 19) Johannes Schindelin
2020-10-21 20:44   ` Junio C Hamano
2020-10-21 20:45     ` Junio C Hamano
2020-10-22 13:16     ` Johannes Schindelin
2020-10-23  8:02 ` Jeff King
2020-10-23 15:27   ` Junio C Hamano
2020-10-23 19:17   ` Elijah Newren
2020-10-27  8:39     ` Jeff King
2020-10-23 14:39 ` ak/corrected-commit-date, was " Jakub Narębski
2020-10-23 16:03   ` Junio C Hamano

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=xmqqtuuobtc4.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).