From: Tejun Heo <htejun@gmail.com>
To: git@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
snemana@yahoo.com, paulus@samba.org, rdunlap@xenotime.net,
mingo@elte.hu
Subject: [ANNOUNCE] mtkdiff-20050801 (with patchkdiff, quiltkdiff, gitkdiff and modified gitk)
Date: Mon, 01 Aug 2005 22:28:47 +0900 [thread overview]
Message-ID: <42EE238F.4050900@gmail.com> (raw)
Hello, guys.
New version of mtkdiff package is available. Changes since last release
(20050514) are.
* patchkdiff added. Idea is from patchview of Randy Dunlap (Hi!).
patchkdiff can show multiple diff files.
* quiltkdiff rewritten in perl. It's faster and doesn't push/pop quilt
repository. Patches are rolled back and applied in a temporary
working directory.
* gitkdiff rewritten in perl. It now works with the new git diff
output format and a bit faster. Also, this version can show
multiple commits. For example, you can do the following.
$ git-rev-list HEAD ^OLD_HEAD | gitkdiff -c -r
* modified gitk-1.2.
For more information...
http://home-tj.org/mtkdiff
Tarball is available at
http://home-tj.org/mtkdiff/files/mtkdiff-20050801.tar.gz
Thanks.
--
tejun
reply other threads:[~2005-08-01 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42EE238F.4050900@gmail.com \
--to=htejun@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rdunlap@xenotime.net \
--cc=snemana@yahoo.com \
/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).