From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Petr Baudis <pasky@suse.cz>, Andreas Gruenbacher <agruen@suse.de>,
B.Steinbrink@gmx.de, git@vger.kernel.org
Subject: Re: [PATCH v4] Introduce %<branch> as shortcut to the tracked branch
Date: Fri, 20 Mar 2009 10:03:43 -0700 [thread overview]
Message-ID: <7v7i2ki0sw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0903201714020.10279@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Fri, 20 Mar 2009 17:17:01 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Often, it is quite interesting to inspect the branch tracked by a given
> branch. This patch introduces a nice notation to get at the tracked
> branch: '%<branch>' can be used to access that tracked branch.
>
> A special shortcut '%' refers to the branch tracked by the current branch.
>
> Suggested by Pasky.
>
> Even if a branch name can legally start with a '%' sign, we can use the
> special character '%' here, as you can always specify the full ref:
> refs/heads/%my-branch (pointed out by doener on IRC).
That is not a good argument, as %<name> is (just like name@{-n} is) a
substitute way to spell the "name" of a branch, not just a random SHA-1,
and to some commands it makes a difference between <branchname> and
refs/heads/<branchname>. The latter is not giving the name of the branch,
but merely a commit object name.
An most obvious one is that "git checkout branchname" and "git checkout
refs/heads/branchname" behave differently. You cannot checkout a branch
called %master after this patch goes in.
Just be honest and say "You may have a branch whose name begins with a '%'
and you cannot refer to it anymore in certain contexts. Too bad. Don't
do it next time you create a new branch". I _can_ buy that argument.
It however asks for a sane escape hatch. You cannot "fix" such branch
names in most obvious ways (if you could, that would be a bug in this %
feature).
(1) git branch -m %master percent-master
We would end up renaming what master tracks to new name.
(2) git branch percent-master refs/heads/%master; git branch -d %master
The first part is a good try, but the latter deletes what master
tracks.
"git update-ref -d refs/heads/%master" needs to replace the second step of
the latter.
next prev parent reply other threads:[~2009-03-20 17:05 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903181448.50706.agruen@suse.de>
2009-03-18 18:26 ` Git {log,diff} against tracked branch? Petr Baudis
2009-03-18 21:12 ` [PATCH] Introduce %<branch> as shortcut to the tracked branch Johannes Schindelin
2009-03-18 21:41 ` Andreas Gruenbacher
2009-03-18 21:46 ` [PATCH v2] " Johannes Schindelin
2009-03-18 21:58 ` Andreas Gruenbacher
2009-03-18 22:43 ` Johannes Schindelin
2009-03-18 22:34 ` Junio C Hamano
2009-03-18 22:46 ` Johannes Schindelin
2009-03-19 14:52 ` Michael J Gruber
2009-03-19 15:17 ` Michael J Gruber
2009-03-20 0:23 ` Johannes Schindelin
2009-03-20 0:38 ` ref name troubles, was " Johannes Schindelin
2009-03-20 0:40 ` Shawn O. Pearce
2009-03-20 0:44 ` Shawn O. Pearce
2009-03-20 5:59 ` Sverre Rabbelier
2009-03-20 9:29 ` [PATCH v3] Introduce BEL<branch> " Johannes Schindelin
2009-03-20 9:42 ` Wincent Colaiuta
2009-03-20 9:54 ` Johannes Schindelin
2009-03-20 12:33 ` Santi Béjar
2009-03-20 12:45 ` Andreas Gruenbacher
2009-03-20 13:05 ` Matthieu Moy
2009-03-20 12:46 ` Johannes Schindelin
2009-03-20 12:53 ` Mikael Magnusson
2009-03-20 14:00 ` Johannes Schindelin
2009-03-20 10:04 ` [PATCH] Document and test the new % shotcut for " Michael J Gruber
2009-03-20 10:31 ` Johannes Schindelin
2009-03-20 10:38 ` Michael J Gruber
2009-03-20 11:16 ` Petr Baudis
2009-03-20 11:48 ` Johannes Schindelin
2009-03-22 17:40 ` Petr Baudis
2009-03-20 14:15 ` Michael J Gruber
2009-03-20 16:17 ` [PATCH v4] Introduce %<branch> as shortcut to " Johannes Schindelin
2009-03-20 17:03 ` Junio C Hamano [this message]
2009-03-20 17:32 ` Johannes Schindelin
2009-03-20 18:02 ` Junio C Hamano
2009-03-20 19:36 ` Jeff King
2009-03-20 20:28 ` Julian Phillips
2009-03-20 20:50 ` Jeff King
2009-03-20 23:08 ` Julian Phillips
2009-03-20 23:20 ` Sverre Rabbelier
2009-03-20 23:41 ` Julian Phillips
2009-03-20 23:45 ` Sverre Rabbelier
2009-03-21 0:35 ` Andreas Gruenbacher
2009-03-21 1:10 ` Miles Bader
2009-03-21 13:24 ` Julian Phillips
2009-03-21 13:28 ` Julian Phillips
2009-03-20 17:08 ` Björn Steinbrink
2009-03-20 6:05 ` ref name troubles, was Re: [PATCH v2] " Jeff King
2009-03-20 6:57 ` Junio C Hamano
2009-03-20 9:30 ` Johannes Schindelin
2009-03-20 11:12 ` Petr Baudis
2009-03-20 11:46 ` Johannes Schindelin
2009-03-20 11:50 ` Petr Baudis
2009-03-20 11:57 ` Johannes Schindelin
2009-03-20 14:31 ` Michael J Gruber
2009-03-20 15:01 ` Johannes Schindelin
2009-03-20 15:12 ` Michael J Gruber
2009-03-20 16:47 ` Junio C Hamano
2009-03-20 19:34 ` Daniel Barkalow
2009-03-20 21:48 ` Johannes Schindelin
2009-03-21 21:00 ` Junio C Hamano
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=7v7i2ki0sw.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=B.Steinbrink@gmx.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=agruen@suse.de \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.