From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Andreas Ericsson <ae@op5.se>, Tom Lanyon <tom@netspot.com.au>,
Karl Chen <quarl@quarl.org>,
Git Mailinglist <git@vger.kernel.org>
Subject: Re: Git config not expanding user home directories
Date: Tue, 30 Sep 2008 23:22:46 -0400 [thread overview]
Message-ID: <20081001032246.GB24513@coredump.intra.peff.net> (raw)
In-Reply-To: <m33ajhsw24.fsf@localhost.localdomain>
On Tue, Sep 30, 2008 at 04:38:46AM -0700, Jakub Narebski wrote:
> There was a patch send to git mailing list adding basic '~' support
> (I think via $ENV{HOME}), and IIRC even ~user support. I don't know
> what happened to those patches (check mailing list archive), but
> most probably it was not accepted because it didn't provide a way
> for scripts to use this functionality, for example via --path option.
There were several rounds, and I thought it was shaping up, but then
no more rounds came. I assume that Karl lost interest (or perhaps we
nitpicked him to death), but I thought at the end of the thread Junio
laid out a plan for the next revision. I guess nobody cared enough about
the feature to implement it after that (though I think I found the final
version acceptable with a minor documentation tweak, I think Junio laid
out a cleaner approach).
The last patch is here, with one of the replies from Junio giving the
aforementioned plan:
http://mid.gmane.org/quack.20080829T0229.lthhc94rwyr_-_@roar.cs.berkeley.edu
-Peff
next prev parent reply other threads:[~2008-10-01 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 10:46 Git config not expanding user home directories Tom Lanyon
2008-09-30 10:49 ` Andreas Ericsson
2008-09-30 11:38 ` Jakub Narebski
2008-10-01 3:22 ` Jeff King [this message]
2008-10-01 7:52 ` Andreas Ericsson
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=20081001032246.GB24513@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=quarl@quarl.org \
--cc=tom@netspot.com.au \
/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).