From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: git@vger.kernel.org
Subject: Re: cvs diff -l equivalent?
Date: Wed, 30 Jul 2008 14:25:22 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807301424271.3277@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080730082030.GA12555@cuci.nl>
On Wed, 30 Jul 2008, 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?
Not without patching, no. When generating a patch, git diff always
recurses.
I suspect adding some kind of "-l" flag would be about five lines of code,
though, so if you really need it... Hint, hint.
Linus
prev parent reply other threads:[~2008-07-30 21:29 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
2008-07-30 20:57 ` Mikael Magnusson
2008-07-30 21:25 ` 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=alpine.LFD.1.10.0807301424271.3277@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=srb@cuci.nl \
/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).