From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Javier.Roucher-Iglesias@ensimag.imag.fr, git@vger.kernel.org,
Javier Roucher <jroucher@gmail.com>,
Pavel Volek <Pavel.Volek@ensimag.imag.fr>,
NGUYEN Kim Thuat <Kim-Thuat.Nguyen@ensimag.imag.fr>,
ROUCHER IGLESIAS Javier <roucherj@ensimag.imag.fr>
Subject: Re: [PATCH_v1] add 'git credential' plumbing command
Date: Mon, 11 Jun 2012 14:18:40 -0400 [thread overview]
Message-ID: <20120611181840.GC20134@sigill.intra.peff.net> (raw)
In-Reply-To: <vpqr4tl4ti9.fsf@bauges.imag.fr>
On Mon, Jun 11, 2012 at 08:02:06PM +0200, Matthieu Moy wrote:
> Jeff King <peff@peff.net> writes:
>
> > It's nice to have an example like this, but there's much detail missing
> > in how the format is specified. However, this format is already
> > documented in the "helpers" section of api-credentials.txt, so it
> > probably makes sense to refer to that document.
>
> I'd do it the other way around. api-credentials.txt is in technical/,
> while the document we're writing will end-up in a man page, which cannot
> link to technical/.
We do so already in a few places:
$ cd Documentation && git grep 'link:technical/'
git.txt:link:technical/api-index.html[GIT API documentation].
gitcredentials.txt:link:technical/api-credentials.html[credentials API] for details.
user-manual.txt:found in link:technical/pack-format.txt[technical/pack-format.txt].
I think the rationale is that you would have the HTML documentation
installed into /usr/share/doc/git-doc or similar, and asciidoc does
correctly generate footnote references from those links. However, I
would be fine with putting the meat of it into git-credential, and
having api-credentials refer back to it. It's easier on the user that
way.
> > git credential --helper=cache fill
> >
> > That will give us more flexibility later down the road.
>
> Actually, this should already be possible with
>
> git -c credential.helper=cache credential fill
>
> I suspect that this feature will never be used outside tests, and if so,
> I don't think it deserves a command-line option.
Yeah, that is even better. The tests could also use test_config. I
would pick whichever of the two is more convenient for a particular
test.
-Peff
next prev parent reply other threads:[~2012-06-11 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 18:45 [PATCH_v1] add 'git credential' plumbing command Javier.Roucher-Iglesias
2012-06-09 19:52 ` konglu
2012-06-10 17:41 ` roucherj
2012-06-10 18:12 ` Matthieu Moy
2012-06-10 6:53 ` Junio C Hamano
2012-06-10 13:16 ` Matthieu Moy
2012-06-10 20:32 ` Jonathan Nieder
2012-06-10 21:02 ` Jonathan Nieder
2012-06-11 15:35 ` Junio C Hamano
2012-06-10 11:56 ` Jeff King
2012-06-11 15:34 ` Junio C Hamano
2012-06-11 15:45 ` Jeff King
2012-06-11 18:02 ` Matthieu Moy
2012-06-11 18:18 ` Jeff King [this message]
2012-06-10 13:18 ` Matthieu Moy
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=20120611181840.GC20134@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Javier.Roucher-Iglesias@ensimag.imag.fr \
--cc=Kim-Thuat.Nguyen@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Pavel.Volek@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=jroucher@gmail.com \
--cc=roucherj@ensimag.imag.fr \
/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).