Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Jun 2001 12:08:46 -0700
From:      "Bruce A. Mah" <bmah@FreeBSD.org>
To:        Nik Clayton <nik@FreeBSD.org>
Cc:        doc@FreeBSD.org, cvs-committers@FreeBSD.org
Subject:   Re: On the recent -i18n changes 
Message-ID:  <200106121908.f5CJ8kl33358@bmah-freebsd-0.cisco.com>
In-Reply-To: <01061218463104.37769@clan.nothing-going-on.org> 
References:  <01061218463104.37769@clan.nothing-going-on.org>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
I've said about all I care to say about what *has* happened or what 
*should* have happened, maybe more than I should have.  But now.....

> Going forward, what do we do?
> 
>  1.  As far as I can see, we don't need to back out the change in doc/.  I
>      haven't yet done a full CVSup and build to test it (cable modem is     
>      down, I'm back to dialup, and it won't be fixed until tomorrow).

doc/ looks pretty good, at least as far as being able to build (I just
did a full build of the HTML docs).

I know little about the web site build, so I can't really comment on 
that.

>  2.  I don't know about the release-notes section of the tree.  As far as 
>      I'm concerned, Bruce is the final authority on that chunk -- if the 
>      change is causing him problems that will take time to resolve then we
>      should back out the change there, live with the fact that it's         
>      inconsistent, and then plan how to remove the inconsistency without
>      introducing world breakage.

Basically, I know how to fix RELNOTESng for 4-STABLE, but what the fix
*is* will depend on the nature of what other actions are being taken.
(RELNOTESng for -CURRENT is OK, as far as I've been able to tell.)  So
one of two things will happen:

1.  If the I18N changes in doc/ get reverted, then there's nothing left
for me to do, because the brokenness will get reverted as well.

2.  If we keep the I18N changes in doc/, I will need a repo-meister to
change some of the tags under src/release/doc, and then I need to patch
three files in RELENG_4 (the same three files that ache patched under
HEAD).  It means that RELENG_4 is going to have a mixture of old-style 
and new-style locale names, but I don't think this is fatal.

Either way I can fix things.  So I'm waiting to hear what we're going 
to do for the rest of doc/ (either by consensus or fiat).  At this 
point, I'm pretty agnostic.

Bruce.



[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: Exmh version 2.3.1+ 05/14/2001

iD8DBQE7Jmi+2MoxcVugUsMRAnr+AJ9qmJcW6Cf0Pj/YnMVKuBBPK+cHTwCeOnpL
kLYj+aFIIHazZ3c7H2SjxFo=
=tz7Y
-----END PGP SIGNATURE-----
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106121908.f5CJ8kl33358>