From: Ryan Anderson <ryan@michonline•com>
To: Junio C Hamano <junkio@cox•net>
Cc: Jonas Fonseca <fonseca@diku•dk>, git@vger•kernel.org
Subject: Re: [PATCH] Add git-annotate(1) and git-blame(1)
Date: Mon, 06 Mar 2006 01:30:46 -0500 [thread overview]
Message-ID: <440BD716.4010400@michonline.com> (raw)
In-Reply-To: <7v3bhwcezy.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
Junio C Hamano wrote:
>Jonas Fonseca <fonseca@diku•dk> writes:
>
>
>
>>Signed-off-by: Jonas Fonseca <fonseca@diku•dk>
>>
>>
>
>Wonderful, but I was hoping the "deathmatch" would leave only
>one that needs to be documented and we could wait documenting
>until then ;-).
>
>
heh. If I'm not mistaken, blame is still lacking rename following (at
least, in master), and annotate is still misrepresenting things on
merges, so we've got a bit of a ways to go still.
--
Ryan Anderson
sometimes Pug Majere
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-03-06 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 5:24 [PATCH] Add git-annotate(1) and git-blame(1) Jonas Fonseca
2006-03-06 5:35 ` Junio C Hamano
2006-03-06 6:30 ` Ryan Anderson [this message]
2006-03-06 11:40 ` Jonas Fonseca
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=440BD716.4010400@michonline.com \
--to=ryan@michonline$(echo .)com \
--cc=fonseca@diku$(echo .)dk \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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