git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
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, 9 Jun 2013 14:13:02 -0400	[thread overview]
Message-ID: <20130609181302.GD810@sigill.intra.peff.net> (raw)
In-Reply-To: <vpq38srtun7.fsf@anie.imag.fr>

On Sun, Jun 09, 2013 at 01:01:48PM +0200, Matthieu Moy wrote:

> > 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.

I was actually thinking along the same lines. I often do something
similar with Git's documentation. When you are tweaking the formatting
or an asciidoc knob, it is useful to diff the rendered output to check
that the changes had the effect you wanted.

I usually have done so by hand, but I actually wonder if "git difftool"
could be used as a wrapper for this (I suspect not, because you have to
deal with the whole build tree, not just individual blobs).

-Peff

  parent reply	other threads:[~2013-06-09 18:13 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
2013-06-09 12:18     ` Benoît Person
2013-06-09 18:13     ` Jeff King [this message]
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=20130609181302.GD810@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=benoit.person@ensimag.fr \
    --cc=celestin.matte@ensimag.fr \
    --cc=git@vger.kernel.org \
    /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).