git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: Something wrong with pickaxe?
Date: Wed, 18 Jan 2006 16:25:17 -0800	[thread overview]
Message-ID: <7v3bjlt66q.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0601181541150.3240@g5.osdl.org> (Linus Torvalds's message of "Wed, 18 Jan 2006 15:55:13 -0800 (PST)")

Linus Torvalds <torvalds@osdl.org> writes:

> So when you use pickaxe, you really want to match the whole line you're 
> looking for - otherwise you'll only see when people add or remove a 
> particular string, not when they change things around it. Even then, if 
> that particular line gets _moved_ (but otherwise is unchanged) pickaxe 
> won't pick it up.

True.  I always feed at least couple of lines to it.

> ... Junio would be open to 
> more friendly pickaxe semantics if the suggested semantics change was 
> accompanied by an actual diff to implement them.

True again.  It is hard to be "more friendly" without actually
generating a diff ;-).

  reply	other threads:[~2006-01-19  0:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 23:23 Something wrong with pickaxe? Johannes Schindelin
2006-01-18 23:55 ` Linus Torvalds
2006-01-19  0:25   ` Junio C Hamano [this message]
2006-01-19  9:12     ` Andreas Ericsson
2006-01-19 18:24       ` Junio C Hamano
2006-01-19 19:10         ` Andreas Ericsson
2006-01-19  2:46   ` Junio C Hamano
2006-01-19  2:59     ` Linus Torvalds
2006-01-19  3:29       ` 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=7v3bjlt66q.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).