On 07/03/2012 03:40 PM, Brian Foster wrote:
On Tuesday 03-July-2012 05:23:29 Hallvard Breien Furuseth wrote:
E.g. if it's hard to teach developers to switch
from B to A, a hook which rejects pushes to B might help.
Whilst we _may_ have problems with some of the
internal developers (this can be managed so I'm
not worried about it), the concern is about the
external users (clients who clone but never push)
becoming confused. Hence the requirement about
continuing to use the same branch name as you are
used to using. That's it! It's that simple.
Maybe create a new branch B (an orphan commit unconnected to the old
branch B) with a single README file telling the person that from now on
they should be using branch A.
Michael
--
Michael Haggerty
mhagger@xxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html