From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Jeff King <peff@peff.net>
Cc: benoit.person@ensimag.fr, git@vger.kernel.org, celestin.matte@ensimag.fr
Subject: Re: [PATCH/RFC] git-remote-mediawiki: new tool to preview local changes without pushing
Date: Sun, 09 Jun 2013 13:01:48 +0200 [thread overview]
Message-ID: <vpq38srtun7.fsf@anie.imag.fr> (raw)
In-Reply-To: <20130609060807.GA8906@sigill.intra.peff.net> (Jeff King's message of "Sun, 9 Jun 2013 02:08:07 -0400")
Jeff King <peff@peff.net> writes:
>> 1- Find the remote name of the current branch's upstream and check if it's a
>> wiki one with its url (ie: mediawiki://)
>> 2- Parse the content of the local file (given as argument) using the distant
>> wiki's API.
>
> Makes sense.
>
>> 3- Retrieve the current page on the distant mediawiki.
>> 4- Merge those those contents.
>
> I'm not sure what these steps are for. You are trying to preview not
> just your local version, but pulling in any changes that have happened
> upstream since the work you built on top of?
Same question here. I'd expect "git mw preview" in a mediawiki workflow
to do what "pdflatex foo && evince foo.pdf" do in a latex workflow: see
in rendered form what I've been doing.
In a latex flow, if I want to see how my local changes merge with the
remote ones, I do "git merge && pdflatex", and I'd do the same with "git
mw".
> I also wonder if it would be useful to be able to specify not only files
> in the filesystem, but also arbitrary blobs. So in 4b above, you could
> "git mw preview origin:page.mw" to see the rendered version of what
> upstream has done.
Next step could even be "git mw diff $from $to", using the wiki to
render the diff. Not a priority, but could be funny.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-06-09 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 21:50 [PATCH/RFC] git-remote-mediawiki: new tool to preview local changes without pushing benoit.person
2013-06-08 19:00 ` Matthieu Moy
2013-06-09 6:12 ` Jeff King
2013-06-09 6:08 ` Jeff King
2013-06-09 11:01 ` Matthieu Moy [this message]
2013-06-09 12:18 ` Benoît Person
2013-06-09 18:13 ` Jeff King
2013-06-09 12:35 ` Benoît Person
2013-06-09 14:37 ` Matthieu Moy
2013-06-09 18:32 ` Jeff King
2013-06-11 21:31 ` Benoît Person
2013-06-11 21:37 ` Jeff King
2013-06-12 6:55 ` Matthieu Moy
2013-06-12 8:55 ` Jeff King
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=vpq38srtun7.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=benoit.person@ensimag.fr \
--cc=celestin.matte@ensimag.fr \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).