From: Junio C Hamano <junkio@cox.net>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-format-patch possible regressions
Date: Thu, 25 May 2006 23:16:42 -0700 [thread overview]
Message-ID: <7v4pzdqpit.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <e5bfff550605252309h2c4b74bcp50b095e09e6c133f@mail.gmail.com> (Marco Costalba's message of "Fri, 26 May 2006 08:09:12 +0200")
"Marco Costalba" <mcostalba@gmail.com> writes:
> I was thinking, probably wrong, that the number prepended in file name
> is used also to disambiguate two patches with the same subject.
What Johannes and I were discussing was the other number -- the
total in the series. IOW, y in "[PATCH x/y]". OTOH, the number
used for disambiguation you care about is x, which is made
adjustable with --start-number patch.
So the way for qgit to use it would become something like this.
Instead of giving a list of ranges like "a..b c..d e..f":
* Run "format-patch a..b"; by reading from its stdout you know
what patches you got -- you count them.
* Run "format-patch --start-number=6 c..d" (if you got 5 out of
a..b);
* Run "format-patch --start-number=n e..f" (now you know the drill).
Then the sequence out of c..d would start with a file 0006-xxxx.txt,
which is what you want for disambiguation.
next prev parent reply other threads:[~2006-05-26 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 19:23 git-format-patch possible regressions Marco Costalba
2006-05-25 19:43 ` Linus Torvalds
2006-05-25 20:10 ` Marco Costalba
2006-05-25 19:56 ` Junio C Hamano
2006-05-25 20:21 ` Marco Costalba
2006-05-25 21:55 ` Johannes Schindelin
2006-05-25 22:18 ` Johannes Schindelin
2006-05-25 23:11 ` Junio C Hamano
2006-05-25 23:28 ` Johannes Schindelin
2006-05-26 6:09 ` Marco Costalba
2006-05-26 6:16 ` Junio C Hamano [this message]
2006-05-26 6:26 ` Jakub Narebski
2006-05-27 9:12 ` Marco Costalba
2006-05-28 9:57 ` Johannes Schindelin
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=7v4pzdqpit.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mcostalba@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).