Platform Team/gatch: Difference between revisions

Created page with "== Summary == Support long or ever standing, all time being on top, downstream patchsets in a Git repository. == Install == Clone Gatch repository: git clone git://git.sugar..."
 
No edit summary
Line 1: Line 1:
== Summary ==
== Summary ==


Support long or ever standing, all time being on top, downstream patchsets in a Git repository.
Support long or ever standing, all time being on top, downstream patchsets in a Git repository. This tool is intended to be lightweight and support only long or ever standing downstream patches.
For the rest of use cases, look for other [[#See_also|alternatives]].


== Install ==
== Install ==
Line 67: Line 68:
''Avoid upstream merge history''
''Avoid upstream merge history''
: Gatch does not break Git history, thus, it is possible to see downstream commits that existed before every upstream merge. It is useful to {{Code|git --hard reset}} sometimes, but might be annoying to see all of them in {{Code|git log}} output. To suppress showing these commits, use {{Code|git log --first-parent}} command.
: Gatch does not break Git history, thus, it is possible to see downstream commits that existed before every upstream merge. It is useful to {{Code|git --hard reset}} sometimes, but might be annoying to see all of them in {{Code|git log}} output. To suppress showing these commits, use {{Code|git log --first-parent}} command.
== See also ==
* [http://www.kernel.org/pub/linux/kernel/people/jsipek/guilt/ guilt]<br>A series of bash scripts which add a quilt-like interface to git.
* [http://www.procode.org/stgit/ stgit]<br>Manage a stack of patches using GIT as a backend.
* [http://repo.or.cz/w/topgit.git topgit]<br>A different patch queue manager.


== Getting involved ==
== Getting involved ==