From: Petr Baudis <pasky@suse.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>,
Andreas Gruenbacher <agruen@suse.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Document and test the new % shotcut for the tracked branch
Date: Sun, 22 Mar 2009 18:40:16 +0100 [thread overview]
Message-ID: <20090322174016.GE8940@machine.or.cz> (raw)
In-Reply-To: <alpine.DEB.1.00.0903201247440.6865@intel-tinevez-2-302>
On Fri, Mar 20, 2009 at 12:48:50PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Fri, 20 Mar 2009, Petr Baudis wrote:
>
> > On Fri, Mar 20, 2009 at 11:31:31AM +0100, Johannes Schindelin wrote:
> > > I had it ready yesterday! But the real problem is not addressed by
> > > your patch, either: '%<branch>' is a legal branch name.
> > >
> > > I briefly considered <branch>^{tracked}, but
> > >
> > > - the ^{} codepath does not try to substitute branch _names_, so we'd
> > > have to duplicate that ^{} detection, and,
> > >
> > > - it is really cumbersome to write.
> >
> > We already have @{N} to do one branch-based substitution, so what about
> > following this convention? Can't we have @{t}?
>
> Have you ever tried a German keyboard layout? You would not say that @{}
> is easy to write if you did.
Interesting, do you really use the regular German keyboard layout while
working in shell or programming? Most Czech people I know [*] use either
the USA layout or Czech programming layout.
> Besides, @{<string>} is already taken for the date-based reflog.
Yes, but some strings can never be dates. ;-)
Has our ref-shed painting fest reached any conclusion yet? I'm not fond
of spending more one-off sequences (~, //, ../, ...) on this, or
anything containing a colon (too confusing, IMHO). It would be nice to
get some generic escaping syntax.
The cleanest way I can think of is declaring ~ a special character and
having <ref>~<letter> as a generic way for ref-based expansions;
master~t would then expand to tracked branch of master.
The only(?) downside is that to mangle HEAD ref, you should write \~t
(but you won't notice your mistake until user 't' appears), but that's
a tough call...
(Should HEAD~t -> $HEAD~t -> master~t -> origin/master or rather
HEAD~t -> origin/HEAD? The former is more intuitive, I guess.)
[*] Since most Czech people I know are UNIX users, it seems...
--
Petr "Pasky" Baudis
The average, healthy, well-adjusted adult gets up at seven-thirty
in the morning feeling just terrible. -- Jean Kerr
next prev parent reply other threads:[~2009-03-22 17:41 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 [this message]
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
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=20090322174016.GE8940@machine.or.cz \
--to=pasky@suse.cz \
--cc=Johannes.Schindelin@gmx.de \
--cc=agruen@suse.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).