From: tom fogal <tfogal@alumni.unh.edu>
To: git@vger.kernel.org
Subject: format-patch: numbered patches from a patch list?
Date: Tue, 21 Jul 2009 20:25:52 -0600 [thread overview]
Message-ID: <auto-000020035874@sci.utah.edu> (raw)
I have a need to generate a numbered sequence of patches from a sparse
sprinkling of patches on a branch. Is there a way to accomplish this?
Basically I want to say, `for the patches at the heads of these sha1s,
give me a numbered sequence.' Currently I take the list of shas that I
want, throw them in a file, and loop over each entry:
for sha in $(cat patches) ; do git format-patch -o a/ ${sha}^..${sha} ; done
This is undesirable because each patch is the first patch in a series,
e.g. "0001-...". A desirable interface would be specifying multiple
disconnected ranges via some separator, say ",".
To hammer it home; given:
... -- A -- B -- C -- D -- E -- F -- G
I'd like a command / line or two of shell which could get me:
the patch that created A: 0001
the patch that created B: 0002
the patch that created E: 0003
the patch that created G: 0004
etc. It'd get confusing if I specified multiple branches. Fortunately
I don't need that use case, and anyway I think just providing a raw
ordering based on timestamp (ignoring branches) would be sufficient for
any (of my) future needs.
The use case for all of this is disconnected repositories that really
shouldn't be. We do `special' merging in subversion, so I do a lot of
trunk work via git-svn, and then I have backporting sessions where I
identify commits which should go on our release branches and put them
there.
Thanks for any ideas,
-tom
next reply other threads:[~2009-07-22 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 2:25 tom fogal [this message]
2009-07-22 2:43 ` format-patch: numbered patches from a patch list? Junio C Hamano
2009-07-22 2:44 ` Jeff King
2009-07-22 2:47 ` tom fogal
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=auto-000020035874@sci.utah.edu \
--to=tfogal@alumni.unh.edu \
--cc=git@vger.kernel.org \
--cc=tfogal@sci.utah.edu \
/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).