All of lore.kernel.org
 help / color / mirror / Atom feed
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 (May 2018, #03; Wed, 23)
Date: Mon, 28 May 2018 14:34:36 +0900	[thread overview]
Message-ID: <xmqq7enol4wj.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BHrzaJ4O0WXJM2YhTMzSx-6nxhHTi4VmL0xXph0ts3Msg@mail.gmail.com> (Elijah Newren's message of "Wed, 23 May 2018 23:39:58 -0700")

Elijah Newren <newren@gmail.com> writes:

> On Wed, May 23, 2018 at 5:02 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Here are the topics that have been cooking.  Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'next'.  The ones marked with '.' do not appear in any of
>> the integration branches, but I am still holding onto them.
>
> I don't see the series posted at
> https://public-inbox.org/git/20180522004327.13085-1-newren@gmail.com/
> (various merge-recursive code cleanups) -- or its predecessor --
> showing up anywhere.  Did it slip through the cracks, by chance?

It does not require any chance for various serieses, especially
their earlier iterations, do not get enough time slots to be
processed soon after they are posted, as there are too many topics,
both patches and discussions, active on the list.

Especially the ones that are designed not to apply to the current
'master', which would give me a strong incentive to ignore them
until the prerequisite topics in flight hits 'master' ;-)

  reply	other threads:[~2018-05-28  5:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  0:02 What's cooking in git.git (May 2018, #03; Wed, 23) Junio C Hamano
2018-05-24  6:39 ` Elijah Newren
2018-05-28  5:34   ` Junio C Hamano [this message]
2018-05-24 19:09 ` Stefan Beller
2018-05-24 19:42 ` Ævar Arnfjörð Bjarmason
2018-05-24 19:50 ` Luke Diamand
2018-05-25 12:31 ` js/empty-config-section-fix, was " Johannes Schindelin
2018-05-28  5:40   ` Junio C Hamano
2018-05-28 11:20     ` Johannes Schindelin
2018-05-29 16:49       ` Jeff King

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=xmqq7enol4wj.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.