From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: roucherj <roucherj@telesun.imag.fr>
Cc: <Javier.Roucher-Iglesias@ensimag.imag.fr>, <git@vger.kernel.org>,
Javier Roucher <jroucher@gmail.com>
Subject: Re: [PATCH/RFC] add git credential login to remote mediawiki
Date: Tue, 12 Jun 2012 17:21:47 +0200 [thread overview]
Message-ID: <vpqsje0mu7o.fsf@bauges.imag.fr> (raw)
In-Reply-To: <303c1249341d6f305d315b0a8d9cd20c@telesun.imag.fr> (roucherj@telesun.imag.fr's message of "Tue, 12 Jun 2012 17:10:05 +0200")
roucherj <roucherj@telesun.imag.fr> writes:
> On Tue, 12 Jun 2012 16:51:18 +0200, Matthieu Moy wrote:
>> Javier.Roucher-Iglesias@ensimag.imag.fr writes:
>>
>>> # MediaWiki API instance, created lazily.
>>> +sub run_credential {
>>
>> How is the code related to the comment right above?
>>
>
> Sorry a old comment, i think it's a cause of git rebase i will erase.
The comment was already there in the code, but it was right above
my $mediawiki;
and therefore meaningful.
> sorry but before it's like:
> + my $Prog = "git credential $op";
> + open2(*Reader, *Writer, $Prog);
> + print Writer $msg;
> + close(Writer);
No it wasn't (this is the expected version). It was "close (Writer);"
with an extra space.
>> Didn't I already mention (twice?) that this declaration was meant to
>> stay right above mw_connect_maybe?
>
> yes but 'ask_credential' used $mediawiki then i think i have to
> declare before 'ask_credential'
But do you have any reason not to declare ask_credential after
mw_connect_maybe?
>>> + run_credential("reject");
>>> +# exit 1;
>>
>> Do you, or do you not want to "exit 1". Either remove this, or
>> uncomment
>> it.
>>
>
> i have comment this line to see the opinion of the community, because
> i ask all the time to authenticate
> but there are few operations who we don't have to authenticate it.
>
> now if we comment this line the login will fail but they will continue
> with the operation (like, git clone)
> and try to do it, if the wiki need to be authenticate will refuse the
> operation if not they will continue.
[...]
>> This means you can't use the wiki anonymously anymore. This is an
>> unacceptable regression.
>
> yes you can use anonymously but login will fail and try to the
> operation, this is the reason because i have comment the 'exit 1'.
But in this case, you still prompt for login and password, right?.
That's weird for the user to have to type a dummy login/password and see
an error message to use a wiki anonymously.
>>> sub mw_connect_maybe {
>>> +
>>> if ($mediawiki) {
>>
>> Why do you add this blank line? (already mentionned)
>>
>
> because we need the structure $mediawiki to get the url if is not
> declare it will return with out doing the operation
I'm talking about the blank line, not the if.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2012-06-12 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 14:42 [PATCH/RFC] add git credential login to remote mediawiki Javier.Roucher-Iglesias
2012-06-12 14:51 ` Matthieu Moy
2012-06-12 15:10 ` roucherj
2012-06-12 15:21 ` Matthieu Moy [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=vpqsje0mu7o.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Javier.Roucher-Iglesias@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=jroucher@gmail.com \
--cc=roucherj@telesun.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