From: Alexandre Julliard <julliard@winehq.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] vc-git.el: Switch to using git-blame instead of git-annotate.
Date: Thu, 05 Oct 2006 11:52:52 +0200 [thread overview]
Message-ID: <87fye39jij.fsf@wine.dyndns.org> (raw)
In-Reply-To: <7v4pujf6mx.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Thu\, 05 Oct 2006 02\:34\:30 -0700")
Junio C Hamano <junkio@cox.net> writes:
> Not that I am preferring the annotate output format over blame's
> native output format. I just wanted to know if the reason you
> did not do -c was because you tried and "blame -c" was not
> compatible as advertised (in which case we have one more thing
> to fix).
As far as I can tell, "blame -c" works fine. I switched because I find
the default blame output nicer, it wastes less horizontal space and
the file contents are properly aligned.
--
Alexandre Julliard
julliard@winehq.org
prev parent reply other threads:[~2006-10-05 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 9:30 [PATCH] vc-git.el: Switch to using git-blame instead of git-annotate Alexandre Julliard
2006-10-05 9:34 ` Junio C Hamano
2006-10-05 9:52 ` Alexandre Julliard [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=87fye39jij.fsf@wine.dyndns.org \
--to=julliard@winehq.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).