From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: nguyenki <nguyenki@ensibm.imag.fr>
Cc: <git@vger.kernel.org>, <roucherj@ensimag.imag.fr>,
<Pavel.Volek@ensimag.imag.fr>
Subject: Re: [PATCH/RFC] Export file attachements in git-remote-mediawiki
Date: Tue, 05 Jun 2012 19:05:44 +0200 [thread overview]
Message-ID: <vpq62b5g047.fsf@bauges.imag.fr> (raw)
In-Reply-To: <59db730bded272b60cbd16806c757660@ensibm.imag.fr> (nguyenki@ensibm.imag.fr's message of "Tue, 05 Jun 2012 19:00:01 +0200")
nguyenki <nguyenki@ensibm.imag.fr> writes:
>>> @@ -642,8 +651,14 @@ sub mw_push_file {
>>> my $old_sha1 = $diff_info_split[2];
>>> my $page_created = ($old_sha1 eq NULL_SHA1);
>>> my $page_deleted = ($new_sha1 eq NULL_SHA1);
>>> + my $file_deleted = ($new_sha1 eq NULL_SHA1);
>>
>> This line looks suspiciously similar to the previous one. Do you need
>> another variable for the same value?
> Yes, it's true. I just want the code to be more visible. Because, when
> we delete a file attachment, it's not a page wiki.
I still don't see a reason to have two variables for the same thing. If
$page_deleted is not a good name, then rename the variable to
something more general (e.g. $path_deleted ?)
>>> + else {
>>> + print STDERR "$complete_file_name is not supported on
>>> this version of Mediawiki.\n"
>>
>> It's not a matter of version, it's a matter of configuration.
> What do you think if i change it like:
> else {
> print STDERR "$complete_file_name is not a permitted file
> type. Check your configuration for more information\n"
That's better, but it doesn't tell the user which configuration to
check (Git's one, or the wiki's one).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-06-05 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 20:49 [PATCH/RFC] Export file attachements in git-remote-mediawiki NGUYEN Kim Thuat
2012-06-04 21:34 ` Matthieu Moy
2012-06-05 17:00 ` nguyenki
2012-06-05 17:05 ` Matthieu Moy [this message]
2012-06-06 22:25 ` nguyenki
2012-06-05 17:11 ` nguyenki
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpq62b5g047.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=Pavel.Volek@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=nguyenki@ensibm.imag.fr \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).