From: Brian Foster <brian.foster@maxim-ic.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>,
git mailing list <git@vger.kernel.org>
Subject: Re: [Q] Branch aliases (synonyms)?
Date: Wed, 4 Jul 2012 09:31:40 +0200 [thread overview]
Message-ID: <4417201.NtYkVMYjv0@laclwks004> (raw)
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/
next prev parent reply other threads:[~2012-07-04 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 10:39 [Q] Branch aliases (synonyms)? Brian Foster
2012-07-03 12:23 ` Hallvard Breien Furuseth
2012-07-03 12:36 ` Hallvard Breien Furuseth
2012-07-03 13:40 ` Brian Foster
2012-07-03 15:29 ` Michael Haggerty
2012-07-04 7:31 ` Brian Foster [this message]
2012-07-05 7:06 ` Brian Foster
2012-07-03 16:22 ` Johan Herland
2012-07-03 17:49 ` Hallvard Breien Furuseth
2012-07-04 7:24 ` Brian Foster
2012-07-04 9:55 ` Hallvard Breien Furuseth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4417201.NtYkVMYjv0@laclwks004 \
--to=brian.foster@maxim-ic.com \
--cc=git@vger.kernel.org \
--cc=h.b.furuseth@usit.uio.no \
--cc=mhagger@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).