From: Joe Perches <joe@perches.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] include/asm-arm/: Spelling fixes
Date: Mon, 17 Dec 2007 12:22:51 -0800 [thread overview]
Message-ID: <1197922971.27386.32.camel@localhost> (raw)
In-Reply-To: <20071217201219.GC13515@fieldses.org>
On Mon, 2007-12-17 at 15:12 -0500, J. Bruce Fields wrote:
> Hope you don't mind my cc'ing the git list:
Nope. Not a bit.
I had patches that were committed in word order that
I wanted to aggregate by subsystem.
I took all the patches, created a branch, committed
all the patches at once, then used these commands:
(patch_order is a directory list)
$ let count=0 ; for line in $(cat patch_order) ; do ((count++)); \
printf -v tmp "%04u-Spelling-%s" $count $line ; \
tmp=${tmp//\//-} ; tmp=${tmp// /}; \
git-format-patch -N --thread --start-number $count -s \
-o patch3 \
--subject-prefix="[PATCH] Spelling: $line" master $line ; done
[converted the subjects appropriately]
$ git-send-email --smtp-server <foo> --smtp-user <bar> \
--from "Joe Perches <joe@perches.com>" \
--to "linux-kernel@vger.kernel.org" \
--cc "Andrew Morton <akpm@linux-foundation.org>" \
--cc-cmd "../get_maintainer.pl --nogit" \
--no-thread --suppress-from patch3
I probably just reversed the "--thread" on
git-format-patch and send-email.
cheers, Joe
next prev parent reply other threads:[~2007-12-17 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5703e57f925f31fc0eb38873bd7f10fc44f99cb4.1197918889.git.joe@perches.com>
[not found] ` <20071217195658.GB13515@fieldses.org>
[not found] ` <1197921847.27386.16.camel@localhost>
2007-12-17 20:12 ` [PATCH] include/asm-arm/: Spelling fixes J. Bruce Fields
2007-12-17 20:22 ` Joe Perches [this message]
2007-12-17 20:51 ` Jeff King
2007-12-17 21:27 ` Junio C Hamano
2007-12-17 23:05 ` Jeff King
2007-12-17 23:12 ` Jeff King
2007-12-17 23:28 ` Junio C Hamano
2008-01-08 11:15 ` Josh Triplett
2008-01-08 11:16 ` Josh Triplett
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=1197922971.27386.32.camel@localhost \
--to=joe@perches.com \
--cc=bfields@fieldses.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).