Jason Merrill <ja...@redhat.com> writes: > On 08/21/2015 04:26 AM, Richard Biener wrote: >> On Thu, Aug 20, 2015 at 10:09 PM, Jason Merrill <ja...@redhat.com> wrote: >>>> ISTM that within that namespace, folks ought to have the freedom to use >>>> whatever works for them. If folks want to create a transient branch, >>>> push-rebase-push on that branch, then later remove it, I tend to think, >>>> why not let them. >>> >>> Makes sense. >> >> Well, I think that all public branches should follow the trunk model - if >> only >> to make merging a dev branch to trunk possible without introducing messy >> history. > > All shared branches, yes, but I think personal branches can be more > volatile. > >> Can we limit the namespace one can create branches in? Like force all >> branches created by $user to be in namespace $user?
git will create new namespaces for its own purpose in the future. If you allow arbitrarily named namespaces clashes will happen. >> So require some super-powers to create a toplevel branch? > > We can. > >> And make [user branches] not automatically pulled? > > We can't control what 'git clone' pulls by default. close pulls everything below refs/heads by default. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
