From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Re: [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file.
Date: Wed, 8 Feb 2006 16:09:50 +0100 [thread overview]
Message-ID: <20060208150950.GA29346@ebar091.ebar.dtu.dk> (raw)
In-Reply-To: <11394103753694-git-send-email-ryan@michonline.com>
On Wed, Feb 08, 2006 at 09:52:55AM -0500, Ryan Anderson wrote:
> Signed-off-by: Ryan Anderson <ryan@michonline.com>
>
> ---
>
> I think this version is mostly ready to go.
>
> Junio, the post you pointed me at was very helpful (once I got around to
> listening to it), but the code it links to is missing - if that's a
> better partial implementation than this, can you ressurrect it
> somewhere? I'd be happy to reintegrate it together.
Does it depends on some ealier patch? I get this:
git]$ git-annotate diff-delta.c
Undefined subroutine &main::all_lines_claimed called at
/home/peter/bin/git-annotate line 124.
The patch was applied to: git version 1.1.6.gd19e-dirty.
Peter
next prev parent reply other threads:[~2006-02-08 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 14:52 [PATCH] Add git-annotate - a tool for annotating files with the revision and person that created each line in the file Ryan Anderson
2006-02-08 15:09 ` Peter Eriksen [this message]
2006-02-08 16:05 ` Johannes Schindelin
2006-02-08 16:35 ` Franck Bui-Huu
2006-02-08 17:45 ` Johannes Schindelin
2006-02-08 19:19 ` Junio C Hamano
2006-02-10 11:25 ` Ralf Baechle
2006-02-10 11:55 ` Andreas Ericsson
2006-02-14 10:51 ` Fredrik Kuivinen
2006-02-08 18:47 ` Randal L. Schwartz
2006-02-09 9:19 ` Andreas Ericsson
2006-02-09 9:57 ` Junio C Hamano
2006-02-09 12:04 ` Franck Bui-Huu
2006-02-09 12:47 ` Andreas Ericsson
2006-02-08 19:09 ` Linus Torvalds
2006-02-08 19:51 ` Junio C Hamano
2006-02-08 21:07 ` Ryan Anderson
2006-02-08 21:45 ` Junio C Hamano
2006-02-10 22:04 ` Ryan Anderson
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=20060208150950.GA29346@ebar091.ebar.dtu.dk \
--to=s022018@student.dtu.dk \
--cc=git@vger.kernel.org \
/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).