git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: cvs diff -l equivalent?
Date: Wed, 30 Jul 2008 18:17:14 +0200	[thread overview]
Message-ID: <20080730161714.GC27166@cuci.nl> (raw)
In-Reply-To: <200807301600.44205.trast@student.ethz.ch>

Thomas Rast wrote:
>Stephen R. van den Berg wrote:
>> Someone popped this question on me.  The closest I got was:

>>    git diff .

>> But that still recurses.  Any solutions without patching?

>Maybe a scripted version?  For just 'git diff .', this should work:

>  git diff $(git ls-files . | grep -v /)

git diff $(git ls-files --exclude-standard . | fgrep -v /)

comes the closest, so it seems.

>That will still do the wrong thing if you diff against an older commit
>with a different list of files.  In that case you need the list of
>files in the other side of the diff too:

>  git diff HEAD^..  -- $(git ls-files . | grep -v /; git ls-tree HEAD^ | cut -f2)

This doesn't seem to do the right thing, it messes up with which commit we
diff.
-- 
Sincerely,
           Stephen R. van den Berg.

How many weeks are there in a lightyear?

  reply	other threads:[~2008-07-30 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30  8:20 cvs diff -l equivalent? Stephen R. van den Berg
2008-07-30 13:53 ` Johannes Schindelin
2008-07-30 15:58   ` Stephen R. van den Berg
2008-07-30 18:18     ` Johannes Schindelin
2008-07-30 14:00 ` Thomas Rast
2008-07-30 16:17   ` Stephen R. van den Berg [this message]
2008-07-30 20:57 ` Mikael Magnusson
2008-07-30 21:25 ` Linus Torvalds

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=20080730161714.GC27166@cuci.nl \
    --to=srb@cuci.nl \
    --cc=git@vger.kernel.org \
    --cc=trast@student.ethz.ch \
    /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).