Differences between version 21 and predecessor to the previous major change of KernelDevelopmentWithGit.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 21 | Last edited on Thursday, November 1, 2007 6:16:14 am | by IanMcDonald | Revert |
| Older page: | version 20 | Last edited on Sunday, April 15, 2007 11:38:26 am | by IanMcDonald | Revert |
@@ -130,7 +130,32 @@
There is a tool to help manage a series of patches called [Stacked Git | http://www.procode.org/stgit/] or stgit for short. The [Debian] [Package] is called <tt>stgit</tt>.
Basically you create a branch (see above) and then manage stacks of patches in this and resync upstream when you want to.
+
+!Mailing patches. ArnaldoMelo says
+<verbatim>
+I use mutt for everything now, did it for years, then tried to use
+thunderbird, evolution, kmail, you name it, ran away screaming back to
+good old mutt + vi.
+
+For sending patches I'll use git-send-email in the next DCCP batch, the
+way it uses reply-to to chain patch series is awesome, and it'll save
+lotsa time by being able to use it together with 'git-format-patch -n
+origin', so, in summary what I do is:
+
+1. git-clone --reference linus-2.6 davem-2.6 acme-2.6
+2. hack away (these days, mostly merge like a turtle :-P)
+3. GIT_AUTHOR_NAME="Gerrit" GIT_AUTHOR_EMAIL="gerrit@..." git-commit -a -s
+4. git-format-patch -n origin
+5. write 0000-patch-series.txt describing the patche series
+6. push to master.kernel.org (that will be propagated to
+ www.kernel.org/git, etc)
+7. git-send-email with 0000-patch-series.txt and what was produced in
+ step #4
+8. rm -rf acme-2.6
+9. hiatus, that thing called Real Work does a blunt, real time preempt
+10. goto #1
+</verbatim>
----
Part of CategoryKernel
