From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Juergen Ruehle" <j.ruehle@bmiag.de>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: Diffs from CVS keyword expansion
Date: Fri, 1 Dec 2006 10:33:03 -0500 [thread overview]
Message-ID: <9e4733910612010733x4dea2451r6fc64d2e867735a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611302340030.3695@woody.osdl.org>
On 12/1/06, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Fri, 1 Dec 2006, Juergen Ruehle wrote:
>
> > Jon Smirl writes:
> > > Anyone have a nice script for suppressing diffs caused by CVS keyword
> > > expansion when someone checked the kernel sources into CVS?
> >
> > I usually just say (with GNU diff)
> >
> > diff -I $$ ...
> >
> > which is crude, but should be enough to get rid of the hunks listed by
> > you.
> >
> > You might also want -x CVS if you have the metadata files.
I don't have the original CVS, just a tarball snapshot with the
keywords expanded.
I'm working with the Freescale iMX21 and the Linux port for it has
never be added to the mainline kernel. I am extracting bits and pieces
of it from various vendor tarballs.
>
> Also, if you are actually _using_ CVS to check it out, use
>
> cvs co -ko
>
> I think, to not check out with keyword expansion at all.
>
> (Also usable with "cvs diff -ko", I think)
>
> Linus
>
> PS. Clueless user alert: I have happily not used CVS in years and years,
> and I might remember that all wrong.
>
--
Jon Smirl
next prev parent reply other threads:[~2006-12-01 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 3:56 Diffs from CVS keyword expansion Jon Smirl
2006-12-01 7:06 ` Juergen Ruehle
2006-12-01 7:44 ` Linus Torvalds
2006-12-01 15:33 ` Jon Smirl [this message]
2006-12-05 12:14 ` Uwe Kleine-Koenig
2006-12-05 19:45 ` Randal L. Schwartz
2006-12-05 19:48 ` Johannes Schindelin
2006-12-06 10:05 ` Uwe Kleine-Koenig
2006-12-06 10:08 ` Randal L. Schwartz
2006-12-05 19:55 ` Junio C Hamano
2006-12-05 20:30 ` Robin Rosenberg
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=9e4733910612010733x4dea2451r6fc64d2e867735a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.ruehle@bmiag.de \
--cc=torvalds@osdl.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).