On 29/11/05, Chuck Lever <cel@netapp.com> wrote: > Cloning a branch means creating a new branch and copying all of the > original branch's patches and its base to it. Like creating a tag, > but this also preserves all the StGIT patches as well. [...] > --- a/stgit/commands/branch.py > +++ b/stgit/commands/branch.py [...] > + print 'Cloning current branch to "%s"...' % clone I would put a comma after this line and add sys.stdout.flush(). So that 'done' is shown on the same line. [...] > --- a/stgit/stack.py > +++ b/stgit/stack.py [...] > + def clone(self, target_series): > + """Clones a series > + """ Wouldn't it be easier to do a recursive copy at the directory level (.git/patches/<branch> into .git/patches/<clone> and .git/refs/bases/<branch> into .git/refs/bases/<clone>)? Is there anything that could go wrong if we do this? -- Catalin - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Dec 02 08:06:33 2005
This archive was generated by hypermail 2.1.8 : 2005-12-02 08:06:39 EST