All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Karl Chen <quarl@quarl.org>
Subject: Re: [PATCH] Expand ~ and ~user in core.excludesfile, commit.template
Date: Tue, 17 Nov 2009 09:53:52 +0100	[thread overview]
Message-ID: <vpqpr7hpm5b.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20091117073426.GB4007@coredump.intra.peff.net> (Jeff King's message of "Tue\, 17 Nov 2009 02\:34\:26 -0500")

Jeff King <peff@peff.net> writes:

> On Mon, Nov 16, 2009 at 11:07:40AM +0100, Matthieu Moy wrote:
>
>> +	of files which are not meant to be tracked.  "~" and "~user"
>> +	are expanded to the user's home directory.  See
>>  	linkgit:gitignore[5].
>
> Reading this, it is not clear to me if:
>
>   1. "~" and "~user" are expanded to the home directory of "user", where
>      "user" is the user running git
>
> or
>
>   2. "~" is expanded to the home directory of the user running git, and
>      an arbitrary "~user" is expanded to that user's home directory.
>
> I would expect (2), since that is how everything else works.

Yes. "user" in the sentence is either the user running Git or the same
string as "user" in "~user". I'm not against your proposal, but I'm
afraid we're making the sentence uselessly heavy, since, as you say,
this ~ and ~user convention is widely spread, and I hardly imagine
someone interpreting the sentence as "if you say ~foo, it will expand
to the home directory of bar".

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  parent reply	other threads:[~2009-11-17  8:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 10:07 [PATCH] Expand ~ and ~user in core.excludesfile, commit.template Matthieu Moy
2009-11-16 22:49 ` Junio C Hamano
2009-11-17  6:49   ` Junio C Hamano
2009-11-17  8:59     ` Matthieu Moy
2009-11-16 23:47 ` Jakub Narebski
2009-11-17  6:22   ` Junio C Hamano
2009-11-17  8:57     ` Matthieu Moy
2009-11-17 13:30       ` Jakub Narebski
2009-11-17  9:30     ` Jakub Narebski
2009-11-17  7:34 ` Jeff King
2009-11-17  7:49   ` Mike Hommey
2009-11-17 21:20     ` Andreas Schwab
2009-11-17 22:16       ` Junio C Hamano
2009-11-18  0:42         ` Andreas Schwab
2009-11-18  7:24         ` Matthieu Moy
2009-11-17  8:53   ` Matthieu Moy [this message]
2009-11-17  8:56     ` Jeff King
2009-11-17 17:24 ` [PATCH v2] " Matthieu Moy
2009-11-18  7:29   ` [PATCH v3] " Matthieu Moy
2009-11-18  8:58     ` [PATCH v4] " Matthieu Moy
2009-11-19 15:21       ` [PATCH] expand_user_path: expand ~ to $HOME, not to the actual homedir Matthieu Moy
2009-11-19 15:23         ` Jeff King
2009-11-19 16:32           ` Matthieu Moy
2009-11-19 18:12       ` [PATCH v4] Expand ~ and ~user in core.excludesfile, commit.template 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=vpqpr7hpm5b.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=quarl@quarl.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.