From: tom fogal <tfogal@alumni.unh.edu>
To: git@vger.kernel.org
Subject: Re: format-patch: numbered patches from a patch list?
Date: Tue, 21 Jul 2009 20:47:30 -0600 [thread overview]
Message-ID: <auto-000020035969@sci.utah.edu> (raw)
In-Reply-To: Your message of "Tue, 21 Jul 2009 20:25:52 MDT." <auto-000020035874@sci.utah.edu>
Answering my own question.
tom fogal <tfogal@alumni.unh.edu> writes:
> 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?
Yep. Duh.
Just generate the patches as I did in my my first mail. Then use
mtime.sh:
#!/bin/sh
for patch in $@ ; do
commitdate=$(head -n 5 ${patch} | \
grep "^Date" | \
cut -d: -f 2-)
touch -d "${commitdate}" ${patch}
shortfn=$(echo "${patch}" | cut -b 1-30)
echo "Changed ${shortfn} to ${commitdate}"
done
to change the modification time of every patch I care about. Now I can
list the files by modification time, achieving exactly what I want.
I really love a full posix environment sometimes.
Sorry for the noise,
-tom
prev parent reply other threads:[~2009-07-22 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 2:25 format-patch: numbered patches from a patch list? tom fogal
2009-07-22 2:43 ` Junio C Hamano
2009-07-22 2:44 ` Jeff King
2009-07-22 2:47 ` tom fogal [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=auto-000020035969@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).