From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
To: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
Cc: Brian Foster <brian.foster@maxim-ic.com>,
git mailing list <git@vger.kernel.org>
Subject: Re: [Q] Branch aliases (synonyms)?
Date: Tue, 03 Jul 2012 14:36:57 +0200 [thread overview]
Message-ID: <2d971099da6c66369be0afb7f8bc19d4@ulrik.uio.no> (raw)
In-Reply-To: <93cfd6eb9045585728dfe649359a103c@ulrik.uio.no>
I wrote:
> Possibly in addition to them using a private symref. In this
> case, 'git symbolic-ref B refs/heads/A' might work better.
Whoops, bad idea - git checkout B then gives a detached HEAD.
Hallvard
next prev parent reply other threads:[~2012-07-03 12:37 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 [this message]
2012-07-03 13:40 ` Brian Foster
2012-07-03 15:29 ` Michael Haggerty
2012-07-04 7:31 ` Brian Foster
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=2d971099da6c66369be0afb7f8bc19d4@ulrik.uio.no \
--to=h.b.furuseth@usit.uio.no \
--cc=brian.foster@maxim-ic.com \
--cc=git@vger.kernel.org \
/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).