git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogan Dawes <lists@dawes.za.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Joe Perches <joe@perches.com>, git@vger.kernel.org
Subject: Re: git and linux kernel source
Date: Mon, 13 Aug 2007 17:32:42 +0200	[thread overview]
Message-ID: <46C0799A.3090707@dawes.za.net> (raw)
In-Reply-To: <20070813152714.GF3122@fieldses.org>

J. Bruce Fields wrote:
> On Thu, Aug 09, 2007 at 07:17:18PM -0400, bfields wrote:
>> On Thu, Aug 09, 2007 at 04:11:46PM -0700, Joe Perches wrote:
>>> 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?
>> Something like
>>
>> 	for each sub/dir:
>> 		git add sub/dir
>> 		git commit -m "use bar not foo in sub/dir"
>>
>> should do it.  (Of course, in the particular case above the patches you
>> ended up with probably wouldn't compile individually.)
> 
> OK, now I feel like I have to ask--you're not seriously considering
> doing anything like that, are you?
> 
> --b.

Have you seen LKML recently? Maybe that will answer your question. (A 
500+ patch mail bomb . . .)

Rogan

  reply	other threads:[~2007-08-13 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 23:11 git and linux kernel source Joe Perches
2007-08-09 23:17 ` 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 [this message]
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=46C0799A.3090707@dawes.za.net \
    --to=lists@dawes.za.net \
    --cc=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=joe@perches.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).