From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] cpufreq: remove CVS keywords
Date: Mon, 19 May 2008 19:06:22 -0400 [thread overview]
Message-ID: <9e4733910805191606y7aa3287le2b461032ad9c97a@mail.gmail.com> (raw)
In-Reply-To: <20080519225807.GE17716@cs181133002.pp.htv.fi>
On 5/19/08, Adrian Bunk <bunk@kernel.org> wrote:
> On Mon, May 19, 2008 at 06:42:21PM -0400, Jon Smirl wrote:
> > On 5/19/08, Adrian Bunk <bunk@kernel.org> wrote:
> > > This patch removes CVS keywords that weren't updated for a long time
> > > from comments.
> > >
> > > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> >
> > Thanks for doing this. I'd love to see all CVS keywords removed from
> > the kernel source.
>
>
> I did only the clear-cut cases in this batch (we even have several
> keywords containing 2007 dates, and if someone actually maintains his
> code in CVS that's legitimate usage), but I'll reduce them further in
> the future.
>
>
> > I've spent countless hour cleaning up kernel
> > patches after various embedded vendors checked their kernel source
> > into CVS and then generated patch sets containing their changes plus
> > all of the expanded keywords.
>
>
> Guess what experience motivated me to do these patches...
The $log ones are the most evil. It is hard to automatically remove
the changes from the diffs.
>
> > Jon Smirl
>
> cu
> Adrian
>
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
--
Jon Smirl
jonsmirl@gmail.com
prev parent reply other threads:[~2008-05-19 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 22:03 Adrian Bunk
2008-05-19 22:09 ` Dave Jones
2008-05-19 22:42 ` Jon Smirl
2008-05-19 22:58 ` Adrian Bunk
2008-05-19 23:06 ` Jon Smirl [this message]
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=9e4733910805191606y7aa3287le2b461032ad9c97a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=bunk@kernel.org \
--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®