From: Jeff King <peff@peff.net>
To: Brian Norris <computersforpeace@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] http: expand http.cookieFile as a path
Date: Fri, 29 Apr 2016 10:12:12 -0400 [thread overview]
Message-ID: <20160429141212.GB26643@sigill.intra.peff.net> (raw)
In-Reply-To: <20160429062357.12647-2-computersforpeace@gmail.com>
On Fri, Apr 29, 2016 at 12:23:57AM -0600, Brian Norris wrote:
> This should handle .gitconfig files that specify things like:
>
> [http]
> cookieFile = "~/.gitcookies"
Seems like a good idea, and the implementation looks obviously correct.
For the documentation:
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index a775ad885a76..d3ef2d3b5d13 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -1660,6 +1660,9 @@ http.cookieFile::
> in the Git http session, if they match the server. The file format
> of the file to read cookies from should be plain HTTP headers or
> the Netscape/Mozilla cookie file format (see linkgit:curl[1]).
> + The value of `http.cookieFile` is subject to tilde expansion: `~/` is
> + expanded to the value of `$HOME`, and `~user/` to the specified user's
> + home directory.
> NOTE that the file specified with http.cookieFile is used only as
> input unless http.saveCookies is set.
I'm not sure if it's a good idea to go into so much detail about
expand_user_path() here. There are a lot of options that use the same
rules, and we probably don't want to go into a complete explanation
inside each option's description. Is there a canonical definition of how
we do expansion in config.txt that we can just reference (and if not,
can we add one)?
-Peff
next prev parent reply other threads:[~2016-04-29 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 6:23 [PATCH 1/2] Documentation: config: improve word ordering for http.cookieFile Brian Norris
2016-04-29 6:23 ` [PATCH 2/2] http: expand http.cookieFile as a path Brian Norris
2016-04-29 14:12 ` Jeff King [this message]
2016-04-29 15:55 ` Brian Norris
2016-04-29 17:48 ` Junio C Hamano
2016-04-29 17:49 ` Jeff King
2016-04-29 17:55 ` Junio C Hamano
2016-04-29 17:56 ` Jeff King
2016-04-29 17:52 ` Junio C Hamano
2016-04-29 17:11 ` Junio C Hamano
2016-04-29 17:16 ` Jeff King
2016-04-29 17:27 ` 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=20160429141212.GB26643@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=computersforpeace@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;
as well as URLs for NNTP newsgroup(s).