From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>, git@vger.kernel.org
Subject: Re: [PATCH v2] config: allow ~/ and ~user/ in include.path value
Date: Thu, 26 Apr 2012 02:19:23 -0400 [thread overview]
Message-ID: <20120426061923.GA22819@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqwr53bmc7.fsf@junio.mtv.corp.google.com>
On Wed, Apr 25, 2012 at 01:14:32PM -0700, Junio C Hamano wrote:
> > +found. The value of `include.path` is subject to tilde expansion: `~/`
> > +is expanded to the value of `$HOME`, and `~user/` to the specified
> > +user's home directory. See below for examples.
> >
> > Example
> > ~~~~~~~
> > @@ -122,6 +124,7 @@ Example
> > [include]
> > path = /path/to/foo.inc ; include by absolute path
> > path = foo ; expand "foo" relative to the current file
> > + path = ~/foo ; expand "foo" in your $HOME directory
>
> Modulo s/~/{tilde}/ in the body text (but not in the displayed example),
> looked good to me, so I queued with two amends.
Thanks, I forgot about that.
I'd like to eventually stop building the documentation with
no-inline-literal. It was an asciidoc7 compatibility thing, but we can
probably drop that now. However, I suspect that would require us to
simultaneously convert all of the `{tilde}` uses back into `~`.
-Peff
prev parent reply other threads:[~2012-04-26 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 11:08 [PATCH] config: allow ~/ and ~user/ in include.path value Matthieu Moy
2012-04-24 18:33 ` [PATCH v2] " Matthieu Moy
2012-04-25 12:00 ` Jeff King
2012-04-25 15:53 ` Matthieu Moy
2012-04-25 20:14 ` Junio C Hamano
2012-04-26 6:19 ` Jeff King [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=20120426061923.GA22819@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).