On Mon, Aug 13, 2007 at 05:32:42PM +0200, Rogan Dawes wrote: > 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 . . .) Yes. And it looks like preparation for doing the above kind of splitting-by-maintainer. Which may not be a sensible thing to do for a variety of reasons that I assume people know. But the patch bomb suggests I shouldn't make that kind of assumption. --b. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
