From: Andreas Ericsson <ae@op5.se>
To: Tom Lanyon <tom@netspot.com.au>
Cc: Git Mailinglist <git@vger.kernel.org>
Subject: Re: Git config not expanding user home directories
Date: Tue, 30 Sep 2008 12:49:30 +0200 [thread overview]
Message-ID: <48E2043A.4000501@op5.se> (raw)
In-Reply-To: <F90667E7-6B06-4B34-B655-3C42ED236D9A@netspot.com.au>
Tom Lanyon wrote:
> Hi all,
>
> Is it normal behavior that git (well at least git-svn) won't expand
> ~user from .gitconfig?
>
Yes. You could add a patch for that though. git-daemon does ~user
expansion since quite a long time back, so there's a function ready
for it. I'd do it by doing something like:
git config --path section.key
so that scripts can get the user-expanded version as well. In-core
applications can call expand_path() or some such on their own, I
think.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-09-30 10:50 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 [this message]
2008-09-30 11:38 ` Jakub Narebski
2008-10-01 3:22 ` Jeff King
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=48E2043A.4000501@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.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).