git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / 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 2020, #08; Sun, 24)
Date: Mon, 25 May 2020 09:22:33 -0700	[thread overview]
Message-ID: <xmqqd06sougm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CABPp-BHxeDQS5QXd5Sf6Ws_58-aze_mes3xRvGZYQNWw3Et3VA@mail.gmail.com> (Elijah Newren's message of "Mon, 25 May 2020 07:55:48 -0700")

Elijah Newren <newren@gmail.com> writes:

> On Sun, May 24, 2020 at 8:35 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.
>>
>> Git 2.27-rc2 will be tagged soon, but most of the topics planned for
>> it are already in 'master'.
>>
>> You can find the changes described here in the integration branches
>> of the repositories listed at
>>
>>     http://git-blame.blogspot.com/p/git-public-repositories.html
>
> Looks like the scissors docfix at
> https://lore.kernel.org/git/20200522142611.1217757-1-newren@gmail.com/
> may have fallen through the cracks.  It's not important for 2.27, but
> could that be picked up at least for pu?

Indeed, as I do not necessarily scan through messages all the way to
the end, when it is clear that patches are discussed and polished by
capable hands.  I'd simply wait for the next round before jumping in
in such a case, and shift the focus to other topics and/or tasks.

I haven't read the documentation patch yet, and I do not see anybody
else reading it, either, so it probably is outside the scope for the
upcoming release.

Thanks for pinging.

  reply	other threads:[~2020-05-25 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  3:22 What's cooking in git.git (May 2020, #08; Sun, 24) Junio C Hamano
2020-05-25 14:55 ` Elijah Newren
2020-05-25 16:22   ` Junio C Hamano [this message]
2020-05-25 17:27 ` Todd Zullinger
2020-05-25 17:53   ` brian m. carlson
2020-05-25 18:13     ` Junio C Hamano
2020-05-26 16:01       ` Todd Zullinger

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqd06sougm.fsf@gitster.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).