git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git and linux kernel source

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Aug 9, 2007, 23:17 UTC
Message-ID
<20070809231718.GH12875@fieldses.org>
In-Reply-To
<1186701106.3073.71.camel@localhost>
On Thu, Aug 09, 2007 at 04:11:46PM -0700, Joe Perches wrote:
Show 9 quoted lines
> 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.)

--b.
Previous: Joe PerchesNext: Joe Perches
Message 2 of 6 in “git and linux kernel source”
  1. Joe PerchesAug 9, 2007
  2. J. Bruce FieldsAug 9, 2007
  3. Joe PerchesAug 10, 2007
  4. J. Bruce FieldsAug 13, 2007
  5. Rogan DawesAug 13, 2007
  6. J. Bruce FieldsAug 13, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.