From: Jakub Narebski <jnareb@gmail.com>
To: "Raoul Bhatia [IPAX]" <r.bhatia@ipax.at>
Cc: git@vger.kernel.org
Subject: Re: feature request: git annotate -w like git blame -w
Date: Fri, 11 Nov 2011 05:57:03 -0800 (PST) [thread overview]
Message-ID: <m3sjlun4o9.fsf@localhost.localdomain> (raw)
In-Reply-To: <4EBD1CF4.7040002@ipax.at>
"Raoul Bhatia [IPAX]" <r.bhatia@ipax.at> writes:
> is it possible to add a "git annotate -w" option like git blame has?
Why not use "git blame -c -w"? `-c' turns on annotate-compatibile
output.
From git-annotate(1) manpage:
The only difference between this command and git-blame(1) is that they use
slightly different output formats, and this command exists only for back-
ward compatibility to support existing scripts, and provide a more familiar
command name for people coming from other SCM systems.
> ps. please reply to me in cc as i'm not subscribed to this list.
This is usual behavior on this list.
--
Jakub Narębski
next prev parent reply other threads:[~2011-11-11 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 13:02 feature request: git annotate -w like git blame -w Raoul Bhatia [IPAX]
2011-11-11 13:57 ` Jakub Narebski [this message]
2011-11-14 16:21 ` Raoul Bhatia [IPAX]
2011-11-14 20:49 ` Junio C Hamano
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=m3sjlun4o9.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=r.bhatia@ipax.at \
/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).