From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Git help for kernel archeology, suppress diffs caused by CVS keyword expansion
Date: Sun, 22 Jul 2007 12:09:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707221205080.3607@woody.linux-foundation.org> (raw)
In-Reply-To: <9e4733910707221148g69d7600bk632abb7452ce9c7c@mail.gmail.com>
On Sun, 22 Jul 2007, Jon Smirl wrote:
>
> It would really be useful if git diff had an option for suppressing
> diffs caused by CVS keyword expansion.
I really think it's not a "git diff" issue, but it might be a "import"
issue.
IOW, I think you'd be a *lot* better off just not importing those things
in the first place (which is what CVS does internally), or possibly
importing them as two trees (ie you'd have the "non-log" version and the
"log expansion" version, so that you can track and compare both).
Doing the thing at "diff" time is certainly possible, but this is simply
much better done as a totally independent preprocessing phase. The diff
handling is already some of the more complex parts (and very central), it
would be much simpler and efficient to not try to make that thing fancier,
and instead solve the problem at the front-end.
Linus
next prev parent reply other threads:[~2007-07-22 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 18:48 Jon Smirl
2007-07-22 19:09 ` Linus Torvalds [this message]
2007-07-22 19:12 ` Jon Smirl
2007-07-22 19:37 ` Linus Torvalds
2007-07-22 19:17 ` David Kastrup
2007-07-22 19:47 ` Jan Engelhardt
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.0.999.0707221205080.3607@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®