Git development
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] do_for_each_ref: perform the same sanity check for leftovers.
Date: Sun, 19 Nov 2006 01:19:05 -0500	[thread overview]
Message-ID: <20061119061905.GB26670@spearce.org> (raw)
In-Reply-To: <7vr6w07ylu.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:
>  * "pickaxe -L'/^static int do_for_each_ref/,+40' refs.c" turns

What's this pickaxe you speak of?  Last I read you deleted it when
you renamed git-pickaxe to git-blame.

Have you reinvented git-pickaxe so soon?  Maybe we could try using
git-longblade next time a new comamnd is being developed?  :-)

-- 

  reply	other threads:[~2006-11-19  6:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19  6:13 [PATCH] do_for_each_ref: perform the same sanity check for leftovers Junio C Hamano
2006-11-19  6:19 ` Shawn Pearce [this message]
2006-11-19  6:22   ` 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=20061119061905.GB26670@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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