Re: ChangeLog entries for sysroot branch, and merge

[Gary V. Vaughan]

Hallo Ralf,
On 28 Aug 2010, at 15:16, Ralf Wildenhues wrote:

> OK to apply to the sysroot branch and merge?
> I'm not sure if I need to ask, so I'll leave a bit of time for comments.

I'm assuming that the ChangeLog entries map to the actual changes?  How
come the ChangeLogs weren't committed at the time of the changes that they
log?

But sure... we don't want changes in the tree without corresponding
ChangeLog entries after all, so please go ahead.

> I don't actually care too much if after the merge, ChangeLog dates are
> not all monotonic.  That's just life with trying to map a graph
> linearly.

Me neither, although our TIMESTAMP is currently taken from the top
date of the ChangeLog, which was designed to help us find the right
state of the tree for any bugreports on unreleased versions.

Actually, I have a patch series that moves to git-version-gen, but
it's fiddly enough that we should wait until after the next release
before merging.  But, at least that means we don't have to worry
about TIMESTAMPS being screwy for too long between the next release
and merging that patch series :-)

> +2010-08-22  Ralf Wildenhues  <address@hidden
> +
> +     fix AIX testsuite regression
> +     * libltdl/config/ltmain.m4sh (func_resolve_sysroot): Partly
> +     revert v2.2.10-83-gc45a288: Do not absolutize path here, only do
> +     sysroot replacement.
> +     (func_mode_link): Adjust.
> +
> +2010-08-22  Charles Wilson  <address@hidden
> +
> +     fix --mode=finish
> +     * libltdl/config/ltmain.m4sh (func_mode_finish): Invert then/else
> +     blocks of the "if $opt_dry_run" conditional.
> +
[[...]]

Cheers,
-- 
Gary V. Vaughan (address@hidden)

PGP.sig
Description: This is a digitally signed message part