From: Junio C Hamano <junkio@cox.net>
To: Ryan Anderson <ryan@michonline.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] 1st pass at git-annotate (not-quite functional, however)
Date: Mon, 23 Jan 2006 00:24:32 -0800 [thread overview]
Message-ID: <7vslrfz70f.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060123080532.GD19212@mythryan2.michonline.com> (Ryan Anderson's message of "Mon, 23 Jan 2006 03:05:33 -0500")
Ryan Anderson <ryan@michonline.com> writes:
> I haven't figured out exactly how I want to handle annotating across
> merges,...
You might want to take a look at the "passing blames around"
algorithm I did for "git blame" loooooooooooooooong time ago.
http://article.gmane.org/gmane.comp.version-control.git/5483
prev parent reply other threads:[~2006-01-23 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 8:05 [RFC] 1st pass at git-annotate (not-quite functional, however) Ryan Anderson
2006-01-23 8:24 ` Junio C Hamano [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=7vslrfz70f.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.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