From: Joe Perches <joe@perches.com>
To: git@vger.kernel.org
Subject: git and linux kernel source
Date: Thu, 09 Aug 2007 16:11:46 -0700 [thread overview]
Message-ID: <1186701106.3073.71.camel@localhost> (raw)
A few linux kernel source and git questions:
What's the best procedure to handle a tree-wide source tranformation?
For instance:
git branch foo2bar
egrep -r -w --include=*.[ch] -l "foo" * | \
xargs perl -pi -e 's/\bfoo\b/bar/msg'
git commit -a -m "use bar not foo"
Is there a way to separate the resultant single patch into multiple
patches by subdirectory? Perhaps some git-rev-parse option?
git-format-patch -p --stat -o outputdir
Is there a way to automatically include the appropriate MAINTAINER and
mailing lists from the MAINTAINERS file for each subdirectory?
git-send-mail --to $APPROPRIATE_MAINTAINER \
-cc linux-kernel@vger.kernel.org
Any ideas or help?
next reply other threads:[~2007-08-09 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 23:11 Joe Perches [this message]
2007-08-09 23:17 ` git and linux kernel source J. Bruce Fields
2007-08-10 1:59 ` Joe Perches
2007-08-13 15:27 ` J. Bruce Fields
2007-08-13 15:32 ` Rogan Dawes
2007-08-13 15:38 ` J. Bruce Fields
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=1186701106.3073.71.camel@localhost \
--to=joe@perches.com \
--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).