KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I am used to Mercurial mq extension to maintain a set of custom patches over the upstream. They can be published as a separate repository aside from the upstream. Now in git I use private branches and rebase , and it works well until I want to share my patches with someone else. In Mercurial the patch queue is an independent repository, and can be published as usual. Bitbucket even offers a patch queue feature to link it to the parent repository. In Git, if I publish a private branch with my patches, I lose the ability to rebase them anymore (unless I break merges), yet the patches need to be updated from time to time. From another SO question I found, that in the Git world StGit is proposed as an equivalent for mq . It is similar in use to mq , but how do I publish a patch queue with StGit? ( stg publish seems to be indended to create a just a new “merge friendly” branch, not to publish the patches themselves) What are other approaches to publish patch queues in Git?
Tags (comma-separated)
Save Edits
Cancel