From: Ryan Anderson <ryan@michonline.com>
To: Ryan Anderson <ryan@michonline.com>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix handling of merges in git-annotate
Date: Mon, 03 Jul 2006 18:34:35 -0700 [thread overview]
Message-ID: <44A9C5AB.1020604@michonline.com> (raw)
In-Reply-To: <11519766021208-git-send-email-ryan@michonline.com>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
Ryan Anderson wrote:
> This 2-patch series is a major overhaul to the way git-annotate calculates the blame for each line.
>
> Instead of parsing each diff in reverse, this uses the output from "git
> diff-tree --combined", so that merges can be handled sanely.
>
I forgot:
Please pull from http://h4x0r5.com/~ryan/git/ryan.git annotate-upstream
--
Ryan Anderson
sometimes Pug Majere
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2006-07-04 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 1:30 [PATCH 0/2] Fix handling of merges in git-annotate Ryan Anderson
2006-07-04 1:30 ` [PATCH 1/2] annotate: Support annotation of files on other revisions Ryan Anderson
2006-07-04 1:30 ` [PATCH 2/2] annotate: Correct most merge following to annotate correctly Ryan Anderson
2006-07-04 8:04 ` [PATCH] t8001-annotate: fix a bash-ism in this test Eric Wong
2006-07-04 8:46 ` Junio C Hamano
2006-07-04 1:34 ` Ryan Anderson [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=44A9C5AB.1020604@michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.