From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Git List" <git@vger.kernel.org>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Hu Keping" <hukeping@huawei.com>,
zhengjunling@huawei.com, zhuangbiaowei@huawei.com,
"Patrick Hemmer" <git@stormcloud9.net>,
"Rafael Ascensao" <rafa.almas@gmail.com>,
"René Scharfe" <l.s.r@web.de>
Subject: Re: [PATCH v2] format-patch: make output filename configurable
Date: Mon, 09 Nov 2020 17:43:37 -0800 [thread overview]
Message-ID: <xmqqzh3q7zqu.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20201110002312.GA1267848@coredump.intra.peff.net> (Jeff King's message of "Mon, 9 Nov 2020 19:23:12 -0500")
Jeff King <peff@peff.net> writes:
> On Mon, Nov 09, 2020 at 11:23:48AM -0800, Junio C Hamano wrote:
>
>> @@ -1822,6 +1825,7 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
>> init_display_notes(¬es_opt);
>> git_config(git_format_config, NULL);
>> repo_init_revisions(the_repository, &rev, prefix);
>> + rev.subject_prefix = fmt_patch_subject_prefix;
>> rev.show_notes = show_notes;
>> memcpy(&rev.notes_opt, ¬es_opt, sizeof(notes_opt));
>> rev.commit_format = CMIT_FMT_EMAIL;
>> @@ -1831,7 +1835,6 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
>> rev.diff = 1;
>> rev.max_parents = 1;
>> rev.diffopt.flags.recursive = 1;
>> - rev.subject_prefix = fmt_patch_subject_prefix;
>> memset(&s_r_opt, 0, sizeof(s_r_opt));
>> s_r_opt.def = "HEAD";
>> s_r_opt.revarg_opt = REVARG_COMMITTISH;
>
> It's not clear to me what these hunks are doing. I'm trying really hard
> to find some subtle reason that we need to init this field sooner, but I
> can't. It really looks like it might be leftover noise.
It indeed was leftover noise and has nothing to do with the output
filename length configurablility (I suspect it is a true no-op).
Thanks.
next prev parent reply other threads:[~2020-11-10 1:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 20:15 [PATCH] Lengthening FORMAT_PATCH_NAME_MAX to 80 Hu Keping
2020-11-05 15:01 ` Jeff King
2020-11-05 21:16 ` Junio C Hamano
2020-11-06 8:51 ` hukeping
2020-11-06 17:45 ` Junio C Hamano
2020-11-06 20:50 ` Junio C Hamano
2020-11-06 21:56 ` [PATCH] format-patch: make output filename configurable Junio C Hamano
2020-11-06 22:05 ` Eric Sunshine
2020-11-09 19:23 ` [PATCH v2] " Junio C Hamano
2020-11-10 0:23 ` Jeff King
2020-11-10 1:43 ` Junio C Hamano [this message]
2020-11-10 2:31 ` hukeping
2020-11-10 2:37 ` Junio C Hamano
2020-11-10 4:44 ` hukeping
2020-11-10 5:40 ` 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
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=xmqqzh3q7zqu.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@stormcloud9.net \
--cc=git@vger.kernel.org \
--cc=hukeping@huawei.com \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=rafa.almas@gmail.com \
--cc=sunshine@sunshineco.com \
--cc=zhengjunling@huawei.com \
--cc=zhuangbiaowei@huawei.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).