Re: [Q] Branch aliases (synonyms)?

From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Jul 3, 2012, 15:29 UTC
Message-ID: <4FF30FD6.6020501@alum.mit.edu>
In-Reply-To: <4261222.bYBuBBxnOa@laclwks004>

On 07/03/2012 03:40 PM, Brian Foster wrote:

Show 11 quoted lines

> 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@alum.mit.edu