From: Jonas Fonseca <fonseca@diku.dk>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add git-annotate(1) and git-blame(1)
Date: Mon, 6 Mar 2006 12:40:07 +0100 [thread overview]
Message-ID: <20060306114007.GA12576@diku.dk> (raw)
In-Reply-To: <7v3bhwcezy.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote Sun, Mar 05, 2006:
> 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 ;-).
Why not let them compete on providing the best documentation as well? ;)
But ok, I can understand your point.
--
Jonas Fonseca
prev parent reply other threads:[~2006-03-06 11:40 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
2006-03-06 11:40 ` Jonas Fonseca [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=20060306114007.GA12576@diku.dk \
--to=fonseca@diku.dk \
--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.