git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
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 15:12:03 -0400	[thread overview]
Message-ID: <9e4733910707221212v2f6cc1c4kf7a35e84f351e4cd@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707221205080.3607@woody.linux-foundation.org>

On 7/22/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> 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.

These diffs are coming from companies doing GPL compliance without
really wanting to comply. CVS servers are not made available.


>
>                         Linus
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2007-07-22 19:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 18:48 Git help for kernel archeology, suppress diffs caused by CVS keyword expansion Jon Smirl
2007-07-22 19:00 ` Johannes Schindelin
2007-07-22 19:10   ` Jon Smirl
2007-07-22 19:15     ` Johannes Schindelin
2007-07-22 19:48       ` Jon Smirl
2007-07-22 21:39         ` Johannes Schindelin
2007-07-22 23:45           ` Jon Smirl
2007-07-22 23:50             ` Johannes Schindelin
2007-07-23  0:11               ` Jon Smirl
2007-07-23  0:37                 ` Johannes Schindelin
2007-07-23 14:44                   ` Jon Smirl
2007-07-23 15:11                     ` Simon 'corecode' Schubert
2007-07-23 20:11                     ` Johannes Schindelin
2007-07-24  0:43                       ` Jon Smirl
2007-07-24  1:06                         ` Jon Smirl
2007-07-24  1:16                         ` Johannes Schindelin
2007-07-24 10:16                           ` Jakub Narebski
2007-07-24 11:26                             ` Johannes Schindelin
2007-07-24 13:08                               ` Jon Smirl
2007-07-22 19:09 ` Linus Torvalds
2007-07-22 19:12   ` Jon Smirl [this message]
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=9e4733910707221212v2f6cc1c4kf7a35e84f351e4cd@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).