Actually, the way the changelog is done in CLFS is rather confusing.
There's the Master changelog, and arch-specific changelogs.  Only
changes that apply to ALL archs are recorded in the master changelog.
Changes done to a single arch is recorded in that arch's changelog.
So, in your case, most likely the change that caused the version bump
was to another arch.  Check the archives of the clfs-commits mailing
list at http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-commits
- the svn commit message will be there, and show exactly what caused
the date change.

Jeremy

On 10/12/06, Justin Knierim <[EMAIL PROTECTED]> wrote:
On Wed, 2006-10-11 at 23:58 -0700, Jonathan Davis wrote:
> Okay, now I'm confused.  I'm certain that I looked in the master
> changelog - particularly since the arch-specific one has basically
> nothing in it.

Yeah, no idea.  Within 30-45 minutes after a commit the render is live,
so who knows, maybe a page was cached or something.

> On a related note, udev appears to have been updated to 102, but the
> lib64 patch for x86_64 multilib doesn't appear to have been put online
> yet.  Thanks for all your hard work.

That is true, for now I copied the 100 to 102 for the ftp repo, but I'm
still waiting from Jim if that is the correct update.

Justin

_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev

_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev

Reply via email to