From: Sean <seanlkml@sympatico.ca>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: ~ and ^
Date: Sun, 13 May 2007 15:49:05 -0400 [thread overview]
Message-ID: <20070513154905.36da94e1.seanlkml@sympatico.ca> (raw)
In-Reply-To: <20070513191350.GB14657@diana.vm.bytemark.co.uk>
On Sun, 13 May 2007 21:13:50 +0200
Karl Hasselström <kha@treskal.com> wrote:
> It seems that ~foo is only expanded to foo's home if there is such a
> user. Since all-numeric users probably aren't common, we can probably
> get away with it.
Someone just mentioned to me that ~# is expanded by Bash if you use the
pushd command to keep a directory stack. So ~1 will stop working
if you use "pushd". Maybe it'd be more confusing than helpful. On the
other hand, there's probably no reason for Git to just give an error
message if it receives a properly escaped lone "~", "~#", or "^".
Sean
next prev parent reply other threads:[~2007-05-13 19:49 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 [this message]
2007-05-13 19:17 ` Sean
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=20070513154905.36da94e1.seanlkml@sympatico.ca \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kha@treskal.com \
/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).