From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jon Smirl <jonsmirl@gmail.com>
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 20:00:36 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707221959100.14781@racer.site> (raw)
In-Reply-To: <9e4733910707221148g69d7600bk632abb7452ce9c7c@mail.gmail.com>
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?
Hth,
Dscho
next prev parent reply other threads:[~2007-07-22 19:00 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 [this message]
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
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=Pine.LNX.4.64.0707221959100.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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).