Re: What's cooking in git.git (Oct 2019, #03; Fri, 11)
- From
Elijah Newren <newren@gmail.com>
- Date
- Oct 11, 2019, 20:39 UTC
- Message-ID
- <CABPp-BF346QbjCyWP7HSP9Lh7mDRgtwtPC8b4mqNv4znUHoGFw@mail.gmail.com>
- In-Reply-To
- <xmqq4l0fgroj.fsf@gitster-ct.c.googlers.com>
On Fri, Oct 11, 2019 at 9:42 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 24 quoted lines
> > Elijah Newren <newren@gmail.com> writes: > > >> * en/fast-imexport-nested-tags (2019-10-04) 8 commits > >> (merged to 'next' on 2019-10-07 at 3e75779e10) > >> + fast-export: handle nested tags > >> ... > >> + fast-export: fix exporting a tag and nothing else > >> > >> Updates to fast-import/export. > >> > >> Will merge to 'master'. > > > > Any chance this will merge down before 2.24.0? I'd really like to see > > and use it within filter-repo. > > A few general guidelines I use are that a typical topic spends 1 > week in 'next' (a trivial one-liner may be there for much shorter > time, an involved multi-patch topic that touches the core part of > the system may have to spend more), that an involved topic that is > not in 'master' by rc0 would not appear in the next release, and > that any topic that is not in 'master' by rc1 needs compelling > reason to be in the next release. So it is cutting a bit too close > for this topic, it seems, but we'll see.
:-(
Did I shoot myself in the foot by being quick to jump on Rene's couple of cosmetic touch-up suggestions he posted over a week after the series was originally posted? In other words, if I hadn't stopped you from merging the series down to next to incorporate those clean-ups[1], would the story have been different?
[1] https://public-inbox.org/git/CABPp-BHvzyLf=Wwhv45qKdKjiTVwHtsMdfA0hd5Ejf5fmhHyPg@mail.gmail.com/