{"thread":{"id":"9460","subject":"git and linux kernel source","startedAt":"2007-08-09T23:11:46Z","lastAt":"2007-08-13T15:38:03Z","messageCount":6,"participants":["Joe Perches","J. Bruce Fields","Rogan Dawes"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"50353","messageId":"1186701106.3073.71.camel@localhost","threadId":"9460","inReplyTo":null,"subject":"git and linux kernel source","fromName":"Joe Perches","fromEmail":"joe@perches.com","sentAt":"2007-08-09T23:11:46Z","receivedAt":"2007-08-09T23:11:46Z","isPatch":false,"sender":{"key":"joe@perches.com","avatar":"https://avatars.githubusercontent.com/u/13122723?v=4"},"body":"A few linux kernel source and git questions:\n\nWhat's the best procedure to handle a tree-wide source tranformation?\nFor instance:\n\n  git branch foo2bar\n  egrep -r -w --include=*.[ch] -l \"foo\" * | \\\n\txargs perl -pi -e 's/\\bfoo\\b/bar/msg'\n  git commit -a -m \"use bar not foo\"\n\nIs there a way to separate the resultant single patch into multiple\npatches by subdirectory?  Perhaps some git-rev-parse option?\n\n  git-format-patch -p --stat -o outputdir\n\nIs there a way to automatically include the appropriate MAINTAINER and\nmailing lists from the MAINTAINERS file for each subdirectory?\n\n  git-send-mail --to $APPROPRIATE_MAINTAINER \\\n\t-cc linux-kernel@vger.kernel.org\n\nAny ideas or help?\n"},{"id":"50354","messageId":"20070809231718.GH12875@fieldses.org","threadId":"9460","inReplyTo":"1186701106.3073.71.camel@localhost","subject":"Re: git and linux kernel source","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-08-09T23:17:18Z","receivedAt":"2007-08-09T23:17:18Z","isPatch":false,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Thu, Aug 09, 2007 at 04:11:46PM -0700, Joe Perches wrote:\n> A few linux kernel source and git questions:\n> \n> What's the best procedure to handle a tree-wide source tranformation?\n> For instance:\n> \n>   git branch foo2bar\n>   egrep -r -w --include=*.[ch] -l \"foo\" * | \\\n> \txargs perl -pi -e 's/\\bfoo\\b/bar/msg'\n>   git commit -a -m \"use bar not foo\"\n\n\n> Is there a way to separate the resultant single patch into multiple\n> patches by subdirectory?  Perhaps some git-rev-parse option?\n\nSomething like\n\n\tfor each sub/dir:\n\t\tgit add sub/dir\n\t\tgit commit -m \"use bar not foo in sub/dir\"\n\nshould do it.  (Of course, in the particular case above the patches you\nended up with probably wouldn't compile individually.)\n\n--b.\n"},{"id":"50370","messageId":"1186711187.3073.75.camel@localhost","threadId":"9460","inReplyTo":"20070809231718.GH12875@fieldses.org","subject":"Re: git and linux kernel source","fromName":"Joe Perches","fromEmail":"joe@perches.com","sentAt":"2007-08-10T01:59:47Z","receivedAt":"2007-08-10T01:59:47Z","isPatch":false,"sender":{"key":"joe@perches.com","avatar":"https://avatars.githubusercontent.com/u/13122723?v=4"},"body":"On Thu, 2007-08-09 at 19:17 -0400, J. Bruce Fields wrote:\n> > Is there a way to separate the resultant single patch into multiple\n> > patches by subdirectory?  Perhaps some git-rev-parse option?\n> Something like\n> \tfor each sub/dir:\n> \t\tgit add sub/dir\n> \t\tgit commit -m \"use bar not foo in sub/dir\"\n> should do it.  (Of course, in the particular case above the patches you\n> ended up with probably wouldn't compile individually.)\n\nNor would it likely survive a git bisect, but it's a start.\nMy goal is to eventually commit by maintainer.\n\nThanks, Joe\n"},{"id":"50637","messageId":"20070813152714.GF3122@fieldses.org","threadId":"9460","inReplyTo":"20070809231718.GH12875@fieldses.org","subject":"Re: git and linux kernel source","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-08-13T15:27:14Z","receivedAt":"2007-08-13T15:27:14Z","isPatch":false,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Thu, Aug 09, 2007 at 07:17:18PM -0400, bfields wrote:\n> On Thu, Aug 09, 2007 at 04:11:46PM -0700, Joe Perches wrote:\n> > A few linux kernel source and git questions:\n> > \n> > What's the best procedure to handle a tree-wide source tranformation?\n> > For instance:\n> > \n> >   git branch foo2bar\n> >   egrep -r -w --include=*.[ch] -l \"foo\" * | \\\n> > \txargs perl -pi -e 's/\\bfoo\\b/bar/msg'\n> >   git commit -a -m \"use bar not foo\"\n> \n> \n> > Is there a way to separate the resultant single patch into multiple\n> > patches by subdirectory?  Perhaps some git-rev-parse option?\n> \n> Something like\n> \n> \tfor each sub/dir:\n> \t\tgit add sub/dir\n> \t\tgit commit -m \"use bar not foo in sub/dir\"\n> \n> should do it.  (Of course, in the particular case above the patches you\n> ended up with probably wouldn't compile individually.)\n\nOK, now I feel like I have to ask--you're not seriously considering\ndoing anything like that, are you?\n\n--b.\n"},{"id":"50638","messageId":"46C0799A.3090707@dawes.za.net","threadId":"9460","inReplyTo":"20070813152714.GF3122@fieldses.org","subject":"Re: git and linux kernel source","fromName":"Rogan Dawes","fromEmail":"lists@dawes.za.net","sentAt":"2007-08-13T15:32:42Z","receivedAt":"2007-08-13T15:32:42Z","isPatch":false,"sender":{"key":"lists@dawes.za.net","avatar":null},"body":"J. Bruce Fields wrote:\n> On Thu, Aug 09, 2007 at 07:17:18PM -0400, bfields wrote:\n>> On Thu, Aug 09, 2007 at 04:11:46PM -0700, Joe Perches wrote:\n>>> A few linux kernel source and git questions:\n>>>\n>>> What's the best procedure to handle a tree-wide source tranformation?\n>>> For instance:\n>>>\n>>>   git branch foo2bar\n>>>   egrep -r -w --include=*.[ch] -l \"foo\" * | \\\n>>> \txargs perl -pi -e 's/\\bfoo\\b/bar/msg'\n>>>   git commit -a -m \"use bar not foo\"\n>>\n>>> Is there a way to separate the resultant single patch into multiple\n>>> patches by subdirectory?  Perhaps some git-rev-parse option?\n>> Something like\n>>\n>> \tfor each sub/dir:\n>> \t\tgit add sub/dir\n>> \t\tgit commit -m \"use bar not foo in sub/dir\"\n>>\n>> should do it.  (Of course, in the particular case above the patches you\n>> ended up with probably wouldn't compile individually.)\n> \n> OK, now I feel like I have to ask--you're not seriously considering\n> doing anything like that, are you?\n> \n> --b.\n\nHave you seen LKML recently? Maybe that will answer your question. (A \n500+ patch mail bomb . . .)\n\nRogan\n"},{"id":"50639","messageId":"20070813153803.GG3122@fieldses.org","threadId":"9460","inReplyTo":"46C0799A.3090707@dawes.za.net","subject":"Re: git and linux kernel source","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-08-13T15:38:03Z","receivedAt":"2007-08-13T15:38:03Z","isPatch":false,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Mon, Aug 13, 2007 at 05:32:42PM +0200, Rogan Dawes wrote:\n> J. Bruce Fields wrote:\n>> On Thu, Aug 09, 2007 at 07:17:18PM -0400, bfields wrote:\n>>> On Thu, Aug 09, 2007 at 04:11:46PM -0700, Joe Perches wrote:\n>>>> A few linux kernel source and git questions:\n>>>>\n>>>> What's the best procedure to handle a tree-wide source tranformation?\n>>>> For instance:\n>>>>\n>>>>   git branch foo2bar\n>>>>   egrep -r -w --include=*.[ch] -l \"foo\" * | \\\n>>>> \txargs perl -pi -e 's/\\bfoo\\b/bar/msg'\n>>>>   git commit -a -m \"use bar not foo\"\n>>>\n>>>> Is there a way to separate the resultant single patch into multiple\n>>>> patches by subdirectory?  Perhaps some git-rev-parse option?\n>>> Something like\n>>>\n>>> \tfor each sub/dir:\n>>> \t\tgit add sub/dir\n>>> \t\tgit commit -m \"use bar not foo in sub/dir\"\n>>>\n>>> should do it.  (Of course, in the particular case above the patches you\n>>> ended up with probably wouldn't compile individually.)\n>> OK, now I feel like I have to ask--you're not seriously considering\n>> doing anything like that, are you?\n>> --b.\n>\n> Have you seen LKML recently? Maybe that will answer your question. (A 500+ \n> patch mail bomb . . .)\n\nYes.  And it looks like preparation for doing the above kind of\nsplitting-by-maintainer.  Which may not be a sensible thing to do for a\nvariety of reasons that I assume people know.  But the patch bomb\nsuggests I shouldn't make that kind of assumption.\n\n--b.\n"}]}