From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Javier.Roucher-Iglesias@ensimag.imag.fr
Cc: 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 v3] add 'git credential' plumbing command
Date: Mon, 11 Jun 2012 21:04:39 +0200 [thread overview]
Message-ID: <vpqehpl4qm0.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1339440294-8010-1-git-send-email-Javier.Roucher-Iglesias@ensimag.imag.fr> (Javier Roucher-Iglesias's message of "Mon, 11 Jun 2012 20:44:54 +0200")
> Subject: Re: [PATCH v3] add 'git credential' plumbing command
I guess you mean v2.
Javier.Roucher-Iglesias@ensimag.imag.fr writes:
> Changes in the version2 vs version1:
These should not go to the commit message, but below the --- below (and
before the diffstat).
> Adding to the next patch, version3:
> · Tests files
If the todo-list isn't empty, then mark your patch as "RFC".
> --- /dev/null
> +++ b/Documentation/git-credential.txt
> @@ -0,0 +1,74 @@
> +git-credential(7)
> +=================
> +
> +NAME
> +----
> +git-credential - Provides and store user credentials to git
Provides -> Provide
I'd remove the "to git" part.
Other than that, I prefer Jeff's version sent yesterday. Any reason not
to use it?
The command still isn't listed in "man git", aka Documentation/git.txt
(I already mentionned it)
> + if (!strcmp(op, "fill")) {
> + credential_fill(&c);
> + if (c.username)
> + printf("username=%s\n", c.username);
> + if (c.password)
> + printf("password=%s\n", c.password);
> + }
See Jeff's remarks. It makes sense to output all fields here
(protocol, path, ...).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-06-11 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 18:44 [PATCH v3] add 'git credential' plumbing command Javier.Roucher-Iglesias
2012-06-11 19:04 ` Matthieu Moy [this message]
2012-06-11 19:12 ` roucherj
2012-06-11 19:07 ` konglu
2012-06-11 19:14 ` roucherj
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=vpqehpl4qm0.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Javier.Roucher-Iglesias@ensimag.imag.fr \
--cc=Kim-Thuat.Nguyen@ensimag.imag.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