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? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Stephen Rothwell | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Arjan van de Ven | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interfaceforon access scanning |
| Patrick McHardy | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Eric W. Biederman | Re: namespace support requires network modules to say "GPL" |
git: | |
