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

git and linux kernel source

From
Joe Perches <joe@perches.com>
Date
Aug 9, 2007, 23:11 UTC
Message-ID
<1186701106.3073.71.camel@localhost>
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: J. Bruce Fields
Message 1 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.