From: "Simon.Cathebras" <Simon.Cathebras@ensimag.imag.fr>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Guillaume Sasdy <guillaume.sasdy@ensimag.imag.fr>,
git@vger.kernel.org, Charles Roussel <charles.roussel@ensimag.fr>,
Simon Perrat <Simon.Perrat@ensimag.imag.fr>,
Charles Roussel <Charles.Roussel@ensimag.imag.fr>,
Julien Khayat <Julien.Khayat@ensimag.imag.fr>
Subject: Re: [PATCH 2/3] Test environment of git-remote-mw
Date: Mon, 04 Jun 2012 16:13:00 +0200 [thread overview]
Message-ID: <4FCCC26C.1050304@ensimag.imag.fr> (raw)
In-Reply-To: <vpqipfa9ehx.fsf@bauges.imag.fr>
On 02/06/2012 12:47, Matthieu Moy wrote:
> "Simon.Cathebras"<Simon.Cathebras@ensimag.imag.fr> writes:
>
>>>> +wiki_getpage () {
>>>> + ../test-gitmw.pl get_page -p "$1" "$2"
>>>> +}
>>> Any reason why test-gitmw.pl and wiki_getpage have this slightly
>>> different API? The perl version has a "-p" flag, and the shell command
>>> has only positionnal arguments.
>> The "-p" flag exists to specify if we have to use the admin login on
>> wiki to do the command.
> (then, maybe --admin would be a better name?)
>
I am ok with this... It would be more understandable.
>> For instance, here we fetch a page from the wiki with Admin privilege.
>> Others arguments remains the same.
> What I don't understand is why you need the flexibility to choose
> between admin and non-admin on the Perl side, and you don't need in on
> the shell side.
>
On one hand, we need to be authentificated as an admin to do some wiki's
operations, like deleting a page for instance. It is needed by the Perl.
On the other hand, we don't need it on the shell side because we believe
that we don't have to bother the user with some authentification
consideration.
I mean, if I intend to delete the page <foo> from wiki, it is easier to
call 'wiki_delete_page foo', than 'wiki_delete_page --user=thingumy
--pass=blahblah foo'.
Does it make sense ? If not, what do you think we should do ?
Simon
--
CATHEBRAS Simon
2A-ENSIMAG
Filière Ingéniérie des Systèmes d'Information
Membre Bug-Buster
next prev parent reply other threads:[~2012-06-04 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 16:30 [PATCH/RFC]Test environment for Git-MediaWiki Simon.Cathebras
2012-05-30 17:04 ` [PATCH 1/3] Script to install, delete and clear a MediaWiki Simon Cathebras
2012-05-30 17:04 ` [PATCH 2/3] Test environment of git-remote-mw Simon Cathebras
2012-05-31 7:17 ` Matthieu Moy
2012-06-01 8:53 ` Simon.Cathebras
2012-06-01 9:02 ` Matthieu Moy
2012-06-01 9:21 ` Matthieu Moy
2012-05-30 17:04 ` [PATCH 3/3] Tests file for git-remote-mediawiki Simon Cathebras
2012-05-31 7:19 ` [PATCH 1/3] Script to install, delete and clear a MediaWiki Matthieu Moy
2012-05-31 18:13 ` [PATCH 1/2] FIX: t9360. NEW test t9361 for git pull and git push Guillaume Sasdy
2012-05-31 18:13 ` [PATCH 2/2] FIX: Syntax of shell and perl scripts and posix compliant Guillaume Sasdy
2012-05-31 18:16 ` [PATCH] " Guillaume Sasdy
2012-05-31 18:27 ` Guillaume Sasdy
2012-05-31 18:31 ` [PATCH 1/3] FIX: cmd_* moved to wiki_* in test-gitmw-lib.sh and other files Guillaume Sasdy
2012-06-01 10:41 ` [PATCH 1/3] Script to install, delete and clear a MediaWiki Guillaume Sasdy
2012-06-01 10:41 ` [PATCH 2/3] Test environment of git-remote-mw Guillaume Sasdy
2012-06-01 11:49 ` Matthieu Moy
2012-06-01 14:43 ` Simon.Cathebras
2012-06-02 10:47 ` Matthieu Moy
2012-06-04 14:13 ` Simon.Cathebras [this message]
2012-06-01 10:41 ` [PATCH 3/3] Tests file for git-remote-mediawiki Guillaume Sasdy
-- strict thread matches above, loose matches on Subject: below --
2012-06-05 13:20 [Git-MediaWiki] Test environment for Git-MediaWiki Simon.Cathebras
2012-06-05 13:25 ` [PATCH 1/3] Script to install, delete and clear a MediaWiki Simon Cathebras
2012-06-05 13:25 ` [PATCH 2/3] Test environment of git-remote-mw Simon Cathebras
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=4FCCC26C.1050304@ensimag.imag.fr \
--to=simon.cathebras@ensimag.imag.fr \
--cc=Charles.Roussel@ensimag.imag.fr \
--cc=Julien.Khayat@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Simon.Perrat@ensimag.imag.fr \
--cc=charles.roussel@ensimag.fr \
--cc=git@vger.kernel.org \
--cc=guillaume.sasdy@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).