From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Oct 2019, #03; Fri, 11)
Date: Sat, 12 Oct 2019 01:42:04 +0900 [thread overview]
Message-ID: <xmqq4l0fgroj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BE4f5f3HyZu9wOyq599JN-n0EMF08di+2V51uxDMEwuGQ@mail.gmail.com> (Elijah Newren's message of "Fri, 11 Oct 2019 08:44:50 -0700")
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.
next prev parent reply other threads:[~2019-10-11 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 7:35 What's cooking in git.git (Oct 2019, #03; Fri, 11) Junio C Hamano
2019-10-11 15:44 ` Elijah Newren
2019-10-11 16:42 ` Junio C Hamano [this message]
2019-10-11 20:39 ` Elijah Newren
2019-10-11 23:52 ` Junio C Hamano
2019-10-12 0:50 ` Junio C Hamano
2019-10-12 21:31 ` ds/sparse-cone, was " Johannes Schindelin
2019-10-15 1:50 ` Eric Wong
2019-10-15 3:20 ` Junio C Hamano
2019-10-15 7:11 ` Eric Wong
2019-10-15 12:54 ` Derrick Stolee
2019-10-16 1:21 ` 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=xmqq4l0fgroj.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.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.