From: Paul Mackerras <paulus@samba.org>
To: Jeff King <peff@peff.net>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] gitk: use --textconv to generate diff text
Date: Tue, 12 May 2009 07:59:37 +1000 [thread overview]
Message-ID: <18952.40905.302916.243355@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20090511091346.GA5685@coredump.intra.peff.net>
Jeff King writes:
> As the original author of the textconv code, I am in favor of this. So
> much so that I even posted basically the same patch before:
>
> http://article.gmane.org/gmane.comp.version-control.git/102523
>
> I had trouble finding much discussion in the archive, but I think it may
> not have been taken because we were in release freeze (and textconv was
> a brand new feature in the release at the time).
Which release did --textconv first appear in?
Paul.
next prev parent reply other threads:[~2009-05-11 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 7:18 [PATCH] gitk: use --textconv to generate diff text Johannes Sixt
2009-05-11 7:34 ` Johannes Sixt
2009-05-11 9:13 ` Jeff King
2009-05-11 21:20 ` Junio C Hamano
2009-05-11 21:59 ` Paul Mackerras [this message]
2009-05-11 22:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18952.40905.302916.243355@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--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.
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).