From: Denton Liu <liu.denton@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #03; Wed, 12)
Date: Wed, 12 Jun 2019 22:05:17 -0400 [thread overview]
Message-ID: <20190613020517.GA15030@archbookpro.localdomain> (raw)
In-Reply-To: <xmqqk1dqigz1.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Wed, Jun 12, 2019 at 03:20:02PM -0700, Junio C Hamano 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.22 final has been tagged.
Thanks for the hard work you put into Git!
>
> 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
>
> --------------------------------------------------
[...]
> --------------------------------------------------
> [New Topics]
Would it be possible for you to queue the "teach branch-specific options
for format-patch" patchset[1]? Even if it doesn't make it in its current
form, I believe that this patchset contains some changes that should be
relatively uncontroversial.
Thanks,
Denton
[1]: https://public-inbox.org/git/cover.1558492582.git.liu.denton@gmail.com/
next prev parent reply other threads:[~2019-06-13 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 22:20 What's cooking in git.git (Jun 2019, #03; Wed, 12) Junio C Hamano
2019-06-13 2:05 ` Denton Liu [this message]
2019-06-13 20:56 ` 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=20190613020517.GA15030@archbookpro.localdomain \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).