git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Git help for kernel archeology, suppress diffs caused by CVS keyword expansion
Date: Sun, 22 Jul 2007 15:10:04 -0400	[thread overview]
Message-ID: <9e4733910707221210t2b2896b5ob4ce7bf95d4a707a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707221959100.14781@racer.site>

On 7/22/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> [culling lkml list, since this is really a Git problem]
>
> 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.
>
> Looks to me slightly a bit like an XY problem.
>
> How about using git-filter-branch to get rid of the expansions?  Or even
> better, if you have access to the CVS server, use the -k option to
> cvsimport?

No access to the server the people handing over the diffs and not
making things easy. You get diffs like this when asking companies to
turn over their changes for GPL compliance purposes. A big source is
from companies building embedded systems., Usually the diffs are
pretty worthless but every once in a while they contain very useful
nuggets (like inadvertently documenting secret hardware features). It
is hard to spot the nuggets in all of the noise.


>
> Hth,
> Dscho
>
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2007-07-22 19:10 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 [this message]
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
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=9e4733910707221210t2b2896b5ob4ce7bf95d4a707a@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).