From: Ryan Anderson <ryan@michonline.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] annotate: Support annotation of files on other revisions.
Date: Mon, 06 Mar 2006 10:44:39 -0500 [thread overview]
Message-ID: <440C58E7.5080402@michonline.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0603061016320.1422@wbgn013.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Johannes Schindelin wrote:
>Hi,
>
>On Sun, 5 Mar 2006, Ryan Anderson wrote:
>
>
>
>>+use Data::Dumper;
>>
>>
>
>You really need this?
>
>
I keep adding it back in when debugging things, and then promptly forget
to remove it when I cull the debugging back out.
It's a core module, so it shouldn't be a significant issue for any porting
--
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 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 11:13 [PATCH] git-blame: Use the same tests for git-blame as for git-annotate Fredrik Kuivinen
2006-03-05 23:32 ` Ryan Anderson
2006-03-06 0:19 ` Junio C Hamano
2006-03-06 0:29 ` Martin Langhoff
2006-03-06 2:43 ` [PATCH] annotate: Support annotation of files on other revisions Ryan Anderson
2006-03-06 4:18 ` Martin Langhoff
2006-03-06 7:49 ` Fredrik Kuivinen
2006-03-06 5:31 ` A Large Angry SCM
2006-03-06 5:40 ` Ryan Anderson
2006-03-06 5:50 ` Shawn Pearce
2006-03-06 6:16 ` Junio C Hamano
2006-03-06 6:32 ` Shawn Pearce
2006-03-06 6:21 ` A Large Angry SCM
2006-03-06 6:28 ` Junio C Hamano
2006-03-06 9:24 ` Johannes Schindelin
2006-03-06 9:18 ` Johannes Schindelin
2006-03-06 15:44 ` Ryan Anderson [this message]
2006-03-06 2:56 ` [PATCH] git-blame: Use the same tests for git-blame as for git-annotate Ryan Anderson
2006-03-06 6:12 ` [PATCH] annotate/blame tests updates Junio C Hamano
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=440C58E7.5080402@michonline.com \
--to=ryan@michonline.com \
--cc=Johannes.Schindelin@gmx.de \
--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 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.