From: Junio C Hamano <gitster@pobox.com>
To: Denton Liu <liu.denton@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #03; Wed, 12)
Date: Thu, 13 Jun 2019 13:56:34 -0700 [thread overview]
Message-ID: <xmqqpnnhurul.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190613020517.GA15030@archbookpro.localdomain> (Denton Liu's message of "Wed, 12 Jun 2019 22:05:17 -0400")
Denton Liu <liu.denton@gmail.com> writes:
> 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.
Hmph. I was under the impression that they were abandoned, allowing
"includeif.onbranch" to supersede it as a more general solution.
Looking back at the discussion thread cited
*1* https://public-inbox.org/git/cover.1558492582.git.liu.denton@gmail.com/
it seems that the more general includeIf topic stirred enough
interest but not those 8 patches from v3 (or from v2). If you feel
strongly enough, re-post them to ignite renewed interest in list
readers' minds, perhaps?
Thanks.
prev parent reply other threads:[~2019-06-13 20:56 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
2019-06-13 20:56 ` Junio C Hamano [this message]
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=xmqqpnnhurul.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@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 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).