From: Sean <seanlkml@sympatico.ca>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: ~ and ^
Date: Sun, 13 May 2007 15:17:09 -0400 [thread overview]
Message-ID: <20070513151709.76b5fc33.seanlkml@sympatico.ca> (raw)
In-Reply-To: <7v8xbssfti.fsf@assigned-by-dhcp.cox.net>
On Sun, 13 May 2007 12:07:21 -0700
Junio C Hamano <junkio@cox.net> wrote:
> Interesting.
>
> At least, "ls ~0" does not seem to get confused by bash to be
> the home directory of the root user, so I do not offhand think
> of a reason not to have ~$n as a synonym to HEAD~$n. Would that
> be useful? I dunno.
Not going to shake the world but it's a small convenience. Would be
a bit nicer if a lone ~ worked as well without escaping, but I'm not
sure you'd accept a patch to assume "~" whenever git is passed the
users home directory as a lone option ;)
> P.S.
>
> Welcome back to the list ;-)
>
Thanks.
Sean
next prev parent reply other threads:[~2007-05-13 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 18:44 ~ and ^ Sean
2007-05-13 19:07 ` Junio C Hamano
2007-05-13 19:13 ` Karl Hasselström
2007-05-13 19:49 ` Sean
2007-05-13 19:17 ` Sean [this message]
2007-05-13 20:31 ` Robin Rosenberg
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=20070513151709.76b5fc33.seanlkml@sympatico.ca \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).