From: "Simon.Cathebras" <Simon.Cathebras@ensimag.imag.fr>
To: konglu@minatec.inpg.fr
Cc: git@vger.kernel.org, Volek Pavel <me@pavelvolek.cz>,
NGUYEN Kim Thuat <Kim-Thuat.Nguyen@ensimag.imag.fr>,
ROUCHER IGLESIAS Javier <roucherj@ensimag.imag.fr>,
Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: [PATCHv1] git-remote-mediawiki: import "File:" attachments
Date: Sat, 09 Jun 2012 01:24:13 +0200 [thread overview]
Message-ID: <4FD2899D.4080407@ensimag.imag.fr> (raw)
In-Reply-To: <20120608190305.Horde.szbWGnwdC4BP0jBJMfN12lA@webmail.minatec.grenoble-inp.fr>
On 08/06/2012 19:03, konglu@minatec.inpg.fr wrote:
>
> "Simon.Cathebras" <Simon.Cathebras@ensimag.imag.fr> a écrit :
>
>> On 08/06/2012 16:22, Pavel Volek wrote:
>>> From: Volek Pavel<me@pavelvolek.cz>
>>>
>>> The current version of the git-remote-mediawiki supports only import
>>> and export
>>> of the pages, doesn't support import and export of file attachements
>>> which are
>>> also exposed by MediaWiki API. This patch adds the functionality to
>>> import the
>>> last versions of the files and all versions of description pages for
>>> these
>>> files.
>>>
>>> Signed-off-by: Pavel Volek<Pavel.Volek@ensimag.imag.fr>
>>> Signed-off-by: NGUYEN Kim Thuat<Kim-Thuat.Nguyen@ensimag.imag.fr>
>>> Signed-off-by: ROUCHER IGLESIAS Javier<roucherj@ensimag.imag.fr>
>>> Signed-off-by: Matthieu Moy<Matthieu.Moy@imag.fr>
>>> ---
>>
>>> contrib/mw-to-git/git-remote-mediawiki | 290
>>> +++++++++++++++++++++++++++------
>>> 1 file changed, 244 insertions(+), 46 deletions(-)
>>
>> I am wondering why are you showing the removal for a v1 patch ?
>
> Why not ? The file already exists on branch master and they are
> working on it.
Makes sense... I didn't notice the deletions were on master, my bad.
> Anyway, the patch applies correctly on master.
> BTW, are you implying that only v2+ patch could have deletions ?
> (a patch is not meant to be applied on the previous version).
Actually, I was just saying that showing corrections on a patche's code
during the development of this one, isn't really necessary.
But if it is concerning a modification of a code in a previous version,
I agree, it is absolutly useful ;).
Simon
--
CATHEBRAS Simon
2A-ENSIMAG
Filière Ingéniérie des Systèmes d'Information
Membre Bug-Buster
prev parent reply other threads:[~2012-06-08 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 14:22 [PATCHv1] git-remote-mediawiki: import "File:" attachments Pavel Volek
2012-06-08 14:42 ` Matthieu Moy
2012-06-08 16:20 ` Simon.Cathebras
2012-06-08 17:03 ` konglu
2012-06-08 23:24 ` Simon.Cathebras [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=4FD2899D.4080407@ensimag.imag.fr \
--to=simon.cathebras@ensimag.imag.fr \
--cc=Kim-Thuat.Nguyen@ensimag.imag.fr \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=konglu@minatec.inpg.fr \
--cc=me@pavelvolek.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.