Sascha Peilicke ([email protected]) wrote: > On Thursday 21 November 2013 08:41:51 Victor Lowther wrote: > > On Thu, Nov 21, 2013 at 6:33 AM, Adam Spiers <[email protected]> wrote: > > > Sascha Peilicke ([email protected]) wrote: > > > > I would also wonder why we append > > > > /master to every branch :-) Why not just "release/roxy" ? Or better > > > > "stable/roxy" which seems like a more common pattern in the git world. > > > > > > Because the original pre-flattened branching model included product > > > info ("openstack-os-build" etc.) in the branch name, and then it got > > > partially moved into the releases/ tree in the main repo, leaving > > > behind the branch naming scheme. I believe Victor is working on > > > > > tidying this up, but I don't yet know how that would work: > > > Having a known suffix at the end of a branch name makes it easier to use > > git show-ref in certain use cases, which is why all the release branches > > end in master. > > But ye poor contributokid has to typee more when he branches a lot. Do you > have some examples?
I'd also appreciate a better understanding of this. This sounds like a case where users are being dictated to by the tools, but it should be the other way around. _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
