From: Brian Foster <brian.foster@maxim-ic.com>
Date: Wed, 04 Jul 2012 07:31:40 GMT
Subject: Re: [Q] Branch aliases (synonyms)?
Message-ID: <4417201.NtYkVMYjv0@laclwks004>
In-Reply-To: <4FF30FD6.6020501@alum.mit.edu>

On Tuesday 03-July-2012 08:29:26 Michael Haggerty wrote:
> 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 [...], 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.

 Hum....  This idea, at first glance, looks
 extremely intriguing (with, perhaps, the minor
 tweak there is also a ‘Makefile’ which shows
 the ‘READ_ME’ and then always “fails”  —  That
 would fit better into how the overall system
 works / is typically used).  I will run it by
 my colleagues, and if they think it can fly,
 will try some tests.  Many Thanks!

cheers!
	-blf-
-- 
Brian Foster
Principal MTS, Software        |  La Ciotat, France
Maxim Integrated Products      |  Web:  http://www.maxim-ic.com/