git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Raoul Bhatia [IPAX]" <r.bhatia@ipax.at>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: feature request: git annotate -w like git blame -w
Date: Mon, 14 Nov 2011 17:21:02 +0100	[thread overview]
Message-ID: <4EC13FEE.2040401@ipax.at> (raw)
In-Reply-To: <m3sjlun4o9.fsf@localhost.localdomain>

On 2011-11-11 14:57, Jakub Narebski wrote:
> "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.

thanks for this clarification. somehow, i missed this part while
scanning the man pages.

thank you and sorry for the noise!
raoul
-- 
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia@ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OG          web.          http://www.ipax.at
Barawitzkagasse 10/2/2/11           email.            office@ipax.at
1190 Wien                           tel.               +43 1 3670030
FN 277995t HG Wien                  fax.            +43 1 3670030 15
____________________________________________________________________

  reply	other threads:[~2011-11-14 16:21 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
2011-11-14 16:21   ` Raoul Bhatia [IPAX] [this message]
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=4EC13FEE.2040401@ipax.at \
    --to=r.bhatia@ipax.at \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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).