- <mathrick_> I'm setting up a workflow for a company that hasn't used any VCS before (ew), and I need to make things simple enough to have them use it
- <mathrick_> one of the things I want to get is to have a "submit" command, which takes changes not present in the submit branch yet, and *merges* them in as a new revision, so that the submit branch, which serves as a central repo / coordination point always receives merges corresponding to logical "features", rather than just having revisions pushed from the dev branches
- <mathrick_> that's both for internal organisation purposes, as well as because they interact with an external SVN repo maintained by a customer; they want the customer to receive changes, but only in coarse "feature" chunks and not the fine-grained revisions the development actually happened in
- <mathrick_> and I want to set it up in a way which doesn't require having two different dev/ and submit/ (to perform the merges in) in addition to bzr://server/repo/central
- <mathrick_> only dev/ and bzr://server/repo/central
- <mathrick_> for that reason I'd like the "submit" tool to do something like create an internal .bzr/branch/submit if it doesn't exist yet, and then use that for merges in a transparent way
- <mathrick_> so, the question: does something comparable exist so that I could set it up with appropriate aliases and plugins, or do I need to cobble up my own plugin for that?
SHARE
TWEET
Untitled
a guest
Nov 2nd, 2012
24
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
RAW Paste Data
