From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Richard Gooch <rgooch@atnf.csiro.au>
Cc: "Edward S. Marshall" <esm@logic.net>,
Rik van Riel <riel@conectiva.com.br>,
esr@thyrsus.com, linux-kernel@vger.kernel.org,
kbuild-devel@lists.sourceforge.net
Subject: Re: Cross-referencing frenzy
Date: Thu, 19 Apr 2001 01:38:37 -0400 [thread overview]
Message-ID: <3ADE79DD.6B94362B@mandrakesoft.com> (raw)
In-Reply-To: <200104190400.f3J40Dm00992@mobilix.atnf.CSIRO.AU> <Pine.LNX.4.21.0104190109480.1685-100000@imladris.rielhome.conectiva> <20010418233618.A28546@labyrinth.local> <200104190506.f3J56ik01292@mobilix.atnf.CSIRO.AU>
Richard Gooch wrote:
> Exactly. A ChangeLog should pre preserved for all time. It is an
> incredibly useful tool. Many times I've gone back and checked when
> something was done, and in relation to other changes before, after or
> around the same time.
agreed
> Except the CONFIG_APM_IGNORE_SUSPEND_BOUNCE was in the apm.c source
> file (in a ChangeLog). So just ignoring Documentation/ won't solve the
> problem.
>
> One trick I've used on my own (non-Linux) code is to insert a space
> after the first underscore. That fools the global search, but leaves
> the essence of the ChangeLog entry. It's a bit hackish, though.
>
> A cleaner solution is to parse the source code, ignoring comment
> blocks. However, that's a bit more work.
Or CC the maintainers, who can manually check, distributing the work :)
The stuff in ChangeLogs is clearly not to be touched. Various
documentation has to be examined manually to determine if its outdated
or not. There is no 100% automatic way to do this.
Jeff
--
Jeff Garzik | "The universe is like a safe to which there is a
Building 1024 | combination -- but the combination is locked up
MandrakeSoft | in the safe." -- Peter DeVries
next prev parent reply other threads:[~2001-04-19 5:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 3:34 Cross-referencing frenzy Eric S. Raymond
2001-04-19 4:00 ` Richard Gooch
2001-04-19 4:11 ` Rik van Riel
2001-04-19 4:36 ` Edward S. Marshall
2001-04-19 5:06 ` Richard Gooch
2001-04-19 5:37 ` Eric S. Raymond
2001-04-19 9:26 ` Rogier Wolff
2001-04-19 13:36 ` [kbuild-devel] " Eric S. Raymond
2001-04-19 15:22 ` Rogier Wolff
2001-04-19 5:38 ` Jeff Garzik [this message]
2001-04-19 5:32 ` Eric S. Raymond
2001-04-19 11:41 ` Alan Cox
2001-04-19 4:49 ` Andreas Dilger
2001-04-19 13:23 ` Mike Castle
2001-04-19 13:36 ` Alan Cox
2001-04-19 17:33 ` Eric S. Raymond
2001-04-19 20:53 ` Jim Treadway
2001-04-19 8:02 ` Russell King
2001-04-19 13:16 ` Eric S. Raymond
2001-04-19 14:17 ` Jeff Garzik
2001-04-19 14:25 ` Eric S. Raymond
2001-04-19 18:49 ` [kbuild-devel] " Peter Samuelson
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=3ADE79DD.6B94362B@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=esm@logic.net \
--cc=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.