git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Junio C Hamano <junkio@cox.net>, Jim Meyering <jim@meyering.net>,
	git@vger.kernel.org
Subject: Re: an option to make "git-diff Z A" prints Z's diff before A's
Date: Thu, 26 Oct 2006 08:16:49 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610260812120.3962@g5.osdl.org> (raw)
In-Reply-To: <20061026084221.GB13780@diana.vm.bytemark.co.uk>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 947 bytes --]



On Thu, 26 Oct 2006, Karl Hasselström wrote:
> 
> A related question: is there a way to limit the path to Z, but
> excluding Z/B? That is, I'm interested in the changes in Z, but not
> the changes in its subdirectory B.

We never did that, no. It's certainly a relevant thing to do, and it would 
be sensible to have a kind of common logic with revision parsing (where a 
caret (^) at the beginning would mean "not"), but at the same time, it's 
not been common enough (read: "I have personally never missed it") to 
actually become an issue.

So I _think_ it would fit fairly well into the current code (just teach 
the stuff that uses "char **pathspec" about that new rule), and it might 
not be too bad. On the other hand, that particular code is pretty dense 
and part of a very core and performance critical subsystem, so unless you 
_really_ want this, you might be better off averting your eyes and just 
ignoring this issue ;)

			Linus

      reply	other threads:[~2006-10-26 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25  7:15 an option to make "git-diff Z A" prints Z's diff before A's Jim Meyering
2006-10-25 19:16 ` Junio C Hamano
2006-10-26  8:42   ` Karl Hasselström
2006-10-26 15:16     ` Linus Torvalds [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=Pine.LNX.4.64.0610260812120.3962@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=jim@meyering.net \
    --cc=junkio@cox.net \
    --cc=kha@treskal.com \
    /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).