From: Sergio <sergio.callegari@gmail.com>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git 1.6.5.5
Date: Sun, 6 Dec 2009 13:47:43 +0000 (UTC) [thread overview]
Message-ID: <loom.20091206T143330-71@post.gmane.org> (raw)
In-Reply-To: 7vtyw4il13.fsf@alter.siamese.dyndns.org
> * In configuration files, a few variables that name paths can begin with
> ~/ and ~username/ and they are expanded as expected. This is not a
> bugfix but 1.6.6 will have this and without backporting users cannot
> easily use the same ~/.gitconfig across versions.
Sorry if posting as a reply to the announcement is improper.
However I am noticing that some kind of shell-like expansion is now allowed in
the config file, wrt home directories, and my wish is somehow related to it.
I wonder if it could be possible in future releases to expand also $HOSTNAME in
fetch/push specs.
The use case is the following. Working on more than one machine (e.g. a
laptop A and a desktop B) you might need to periodically push to a server C and
like to share the same config on both machines. Having $HOSTNAME expansion,
whatever machine you push from, you can say git push C and have the branches go
on remote/A or remote/B automatically on the server.
Sergio
prev parent reply other threads:[~2009-12-06 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 8:06 [ANNOUNCE] Git 1.6.5.5 Junio C Hamano
2009-12-06 13:47 ` Sergio [this message]
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=loom.20091206T143330-71@post.gmane.org \
--to=sergio.callegari@gmail.com \
--cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox