From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Improve collection of information for format-patch --cover-letter
Date: Mon, 25 Feb 2008 16:07:21 -0800 [thread overview]
Message-ID: <7v1w70h96u.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0802251822240.19024@iabervon.org> (Daniel Barkalow's message of "Mon, 25 Feb 2008 18:24:17 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> ... Note that the single boundary test is empirical, not
> theoretical; even a -2 limiting condition will give a diffstat if there's
> only one boundary commit in this particular case.
It is unclear what "a -2 limiting condition" means here...
> @@ -679,21 +682,19 @@ static void make_cover_letter(struct rev_info *rev,
>
> strbuf_release(&sb);
>
> + shortlog_init(&log);
> + for (i = 0; i < nr; i++)
> + shortlog_add_commit(&log, list[i]);
> +
> + shortlog_output(&log);
> +
Nice ;-)
> @@ -962,7 +957,15 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix)
>
> if (prepare_revision_walk(&rev))
> die("revision walk setup failed");
> + rev.boundary = 1;
> while ((commit = get_revision(&rev)) != NULL) {
> + if (commit->object.flags & BOUNDARY) {
> + fprintf(stderr, "Boundary %s\n", sha1_to_hex(commit->object.sha1));
Leftover debugging?
next prev parent reply other threads:[~2008-02-26 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 23:24 [PATCH 2/2] Improve collection of information for format-patch --cover-letter Daniel Barkalow
2008-02-26 0:07 ` Junio C Hamano [this message]
2008-02-26 16:27 ` Daniel Barkalow
2008-02-26 18:46 ` Junio C Hamano
2008-02-28 6:18 ` [PATCH] format-patch: remove a leftover debugging message Junio C Hamano
2008-02-28 15:20 ` Daniel Barkalow
2008-02-26 9:19 ` [PATCH 2/2] Improve collection of information for format-patch --cover-letter Junio C Hamano
2008-02-26 9:24 ` 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=7v1w70h96u.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
/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).