Platform Team/gatch: Difference between revisions
No edit summary |
m →Summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
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. | 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 | For the rest of use cases, look for the [[#See_also|alternatives]]. | ||
== Install == | == Install == | ||
| Line 64: | Line 64: | ||
''Upstream merge right after clone'' | ''Upstream merge right after clone'' | ||
: {{Code|init}} command keeps all information regarding upstream repository and branch in {{Code|.sweets/gatch*}} files. So, it is possible to clone downstream branch and run {{Code|merge}} command, gatch will add upstream remote if it absent in local repository. | : {{Code|init}} command keeps all information regarding upstream repository and branch in {{Code|.sweets/gatch*}} files controlled by git. So, it is possible to clone downstream branch and run {{Code|merge}} command, gatch will add upstream remote if it absent in local repository. | ||
''Avoid upstream merge history'' | ''Avoid upstream merge history'' | ||