[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ChangeLog.2 missing

From: Per Cederqvist
Subject: Re: ChangeLog.2 missing
Date: 17 May 2003 13:02:07 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

"Paul D. Smith" <address@hidden> writes:

> %% Per Cederqvist <address@hidden> writes:
>   pc> The ChangeLog file in make-3.80 ends with the line "See
>   pc> ChangeLog.2 for earlier changes.", but that file does not exist in
>   pc> the make-3.80 tar archive.
> I did this on purpose, actually, just like the ChangeLog.1 is not
> shipped with the tarball.  They're very large.  You have to go to the
> CVS archive (note you can also use the Savannah web-based CVS browser)
> to get those older ChangeLog files.
> If there are real issues with this I'll reconsider.

OK.  That makes sense, even if I personally like to have instant
access to all the old logs.  I have occasionally found that useful in
the Emacs distribution.

Perhaps the ChangeLog file could include a pointer to the older file:

        See ChangeLog.2, available in the CVS repository at
        http://savannah.gnu.org/cvs/?group=make, for earlier changes.

I would also suggest that this entry be moved from ChangeLog.2 to
ChangeLog, so that it is clear that all changes between 3.79.1 and
3.80 are present in the distributed ChangeLog:

> 2000-06-23  Paul D. Smith  <address@hidden>
>       * main.c (main): Replace EXIT_SUCCESS, EXIT_FAILURE, and
>       * make.h: Define these macros.
>       * Version 3.79.1 released.
>       * configure.in: Add a new option, --disable-nsec-timestamps, to
>       avoid using sub-second timestamps on systems that support it.  It
>       can lead to problems, e.g. if your makefile relies on "cp -p".
>       * README.template: Document the issue with "cp -p".
>       * config.guess, config.sub: Updated.

The change from EXIT_SUCCESS et c to MAKE_SUCCESS et c was actually
made between the 3.79.1 version and the 3.80 version, and not included
in any distributed ChangeLog.  I guess that this was not what you
intended.  (But I might the only person in the world that cares about
old ChangeLog entries in programs I don't do development work on...)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]