From: Jonathan Nieder <jrnieder@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Junio C Hamano <gitster@pobox.com>,
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: Sun, 10 Jun 2012 16:02:24 -0500 [thread overview]
Message-ID: <20120610210224.GA3112@burratino> (raw)
In-Reply-To: <20120610203259.GA2380@burratino>
Jonathan Nieder wrote:
> Matthieu Moy wrote:
>> Junio C Hamano <gitster@pobox.com> writes:
>>> Does "git credential" need to have a git repository (i.e. run in a
>>> git repository or in a working tree that is controlled by one)?
>>
>> It shouldn't (hence, should use RUN_SETUP_GENTLY).
>
> Rather, that means it should use 0:
>
> { "credential", cmd_credential },
... and it turns out I'm talking nonsense. RUN_SETUP_GENTLY would
be a sensible choice indeed, to allow the command to discover the
current repository and read .git/config from there indeed.
Sorry for the confusion,
Jonathan
next prev parent reply other threads:[~2012-06-10 21:02 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 [this message]
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
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=20120610210224.GA3112@burratino \
--to=jrnieder@gmail.com \
--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=gitster@pobox.com \
--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).