# feature request: git annotate -w like git blame -w 4 messages from 2011-11-11 to 2011-11-14. Participants: Raoul Bhatia [IPAX], Jakub Narebski, Junio C Hamano. Thread: https://gitlist.dev/t/28912 ## Raoul Bhatia [IPAX], 2011-11-11 13:02 Subject: feature request: git annotate -w like git blame -w Message-ID: <4EBD1CF4.7040002@ipax.at> URL: https://gitlist.dev/e/4EBD1CF4.7040002%40ipax.at ``` hi! is it possible to add a "git annotate -w" option like git blame has? thanks, raoul ps. please reply to me in cc as i'm not subscribed to this list. -- ____________________________________________________________________ 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 ____________________________________________________________________ ``` ## Jakub Narebski, 2011-11-11 13:57 Subject: Re: feature request: git annotate -w like git blame -w Message-ID: URL: https://gitlist.dev/e/m3sjlun4o9.fsf%40localhost.localdomain In-Reply-To: <4EBD1CF4.7040002@ipax.at> ``` "Raoul Bhatia [IPAX]" 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 ``` ## Raoul Bhatia [IPAX], 2011-11-14 16:21 Subject: Re: feature request: git annotate -w like git blame -w Message-ID: <4EC13FEE.2040401@ipax.at> URL: https://gitlist.dev/e/4EC13FEE.2040401%40ipax.at In-Reply-To: ``` On 2011-11-11 14:57, Jakub Narebski wrote: > "Raoul Bhatia [IPAX]" 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 ____________________________________________________________________ ``` ## Junio C Hamano, 2011-11-14 20:49 Subject: Re: feature request: git annotate -w like git blame -w Message-ID: <7vvcqmig52.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vvcqmig52.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Jakub Narebski writes: > "Raoul Bhatia [IPAX]" 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. Somebody may want to compare git-blame.txt and git-annotate.txt in Documentation/, notice that they share blame-options.txt and that the former has accumulated option descriptions for a few more options that should have been placed in blame-options.txt, and then prepare a patch to improve the documentation? Hint, hint... I *think* '-c', '-f', and '-n' are blame-only options but all others would work with annotate (whoever is doing the patch needs to verify this, though). ```