/[gentoo]/xml/htdocs/proj/en/glep/glep-0042.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0042.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.4 Revision 1.14
1GLEP: 42 1GLEP: 42
2Title: Critical News Reporting 2Title: Critical News Reporting
3Version: $Revision: 1.4 $ 3Version: $Revision: 1.14 $
4Author: Ciaran McCreesh <ciaranm@gentoo.org> 4Author: Ciaran McCreesh <ciaranm@gentoo.org>,
5 Stephen Bennett <spb@gentoo.org>,
6 Zach Medico <zmedico@gentoo.org>
5Last-Modified: $Date: 2005/12/11 01:38:18 $ 7Last-Modified: $Date: 2010/02/22 11:38:26 $
6Status: Draft 8Status: Final
7Type: Standards Track 9Type: Standards Track
8Content-Type: text/x-rst 10Content-Type: text/x-rst
9Created: 31-Oct-2005 11Created: 31-Oct-2005
10Post-History: 1-Nov-2005, 5-Nov-2005, 7-Nov-2005, 11-Dec-2005 12Post-History: 1-Nov-2005, 5-Nov-2005, 7-Nov-2005, 11-Dec-2005, 13-Dec-2005, 18-Dec-2005, 5-Jan-2006, 2-Mar-2006, 6-Mar-2006, 12-Jun-2006, 5-Sep-2006
11 13
12Abstract 14Abstract
13======== 15========
14 16
15This GLEP proposes a new way of informing users about important updates and news 17This GLEP proposes a new way of informing users about important updates and news
16regarding tree-related items. 18related to the tree.
17 19
18Motivation 20Motivation
19========== 21==========
20 22
21Although most package updates are clean and require little user action, 23Although most package updates are clean and require little user action,
22occasionally an upgrade requires user intervention during the upgrade process. 24occasionally an upgrade requires user intervention. Recent examples of the
23Recent examples of the latter include the ``gcc-3.4`` stabilisation on ``x86`` 25latter include the ``gcc-3.4`` stabilisation on ``x86`` and the ``mysql-4.1``
24and the ``mysql-5`` database format changes. 26database format changes.
25 27
26There are currently several ways of delivering important news items to our 28There are currently several ways of delivering important news items to our
27users, none of them particularly effective: 29users, none of them particularly effective:
28 30
29* Gentoo Weekly News 31* Gentoo Weekly News
30* The ``gentoo-announce``, ``gentoo-user`` and ``gentoo-dev`` mailing lists 32* The ``gentoo-announce``, ``gentoo-user`` and ``gentoo-dev`` mailing lists
31* The Gentoo Forums 33* The Gentoo Forums
32* The main Gentoo website 34* The main Gentoo website
33* RSS feeds of Gentoo news 35* RSS feeds of Gentoo news
36* ``einfo`` and ``ewarn`` messages in ``pkg_setup`` or ``pkg_postinst``
34 37
35A more reliable way of getting news of critical updates out to users is required 38A more reliable way of getting news of critical updates out to users is required
36to avoid repeats of the various recent upgrade debacles. This GLEP proposes a 39to avoid repeats of various prior upgrade debacles. This GLEP proposes a
37solution based around pushing news items out to the user via the ``rsync`` tree. 40solution based around pushing news items out to the user via the ``rsync`` tree.
38 41
39.. Important:: This GLEP does not seek to replace or modify ``einfo`` messages 42.. Important:: This GLEP does not seek to replace or modify ``einfo`` messages
40 which are displayed post-install. That is a separate issue which is handled 43 which are displayed post-install. That is a separate issue which is handled
41 by ``elog`` [#bug-11359]_. 44 by ``elog`` [#bug-11359]_.
51 given ample warning to plan difficult upgrades and changes, rather than only 54 given ample warning to plan difficult upgrades and changes, rather than only
52 being told just before action is necessary. 55 being told just before action is necessary.
53 56
54No user subscription required 57No user subscription required
55 It has already been demonstrated [#forums-apache2]_ that many users do not 58 It has already been demonstrated [#forums-apache2]_ that many users do not
56 read the ``gentoo-announce`` mailing list or ``RSS`` feeds. A solution which 59 read the ``gentoo-announce`` mailing list or ``RSS`` feeds. A solution that
57 requires subscription has no advantage over current methods. 60 requires subscription has no advantage over current methods.
58 61
59No user monitoring required 62No user monitoring required
60 It has already been demonstrated [#forums-apache2]_ that many users do not 63 It has already been demonstrated [#forums-apache2]_ that many users do not
61 read news items posted to the Gentoo website, or do not read news items 64 read news items posted to the Gentoo website, or do not read news items
133 informing the user that there are unread news items. 136 informing the user that there are unread news items.
134 137
1356. The news item is handled by the user's choice of news item reader. See `News 1386. The news item is handled by the user's choice of news item reader. See `News
136 Item Clients`_. 139 Item Clients`_.
137 140
141Required Portage Enhancements
142-----------------------------
143
144The following extensions to Portage are required:
145
146* Every repository (including overlays) will require a unique identifier. It is
147 assumed that an identifier will be a string consisting of characters from
148 ``a`` to ``z``, ``A`` to ``Z``, ``0`` to ``9``, ``+`` (plus), ``-`` (hyphen)
149 ``_`` (underscore).
150
151* Portage must provide a way for external programs to obtain a list of all
152 repository identifiers for a given system. It is assumed that this will be in
153 the form of a ``portageq`` command (e.g. ``portageq get_repo_ids``).
154
155* Portage must provide a way for external programs to obtain the base path for
156 a repository with a given ID. It is assumed that this will be in the form of
157 a ``portageq`` command (e.g. ``portageq get_repo_root gentoo-x86``).
158
159* Portage must extend ``portageq has_version`` to support restrictions to a
160 given repository ID.
161
162* Portage must extend ``portageq`` to implement a command which returns whether
163 or not the profile used for a given repository ID is exactly the given profile
164 (e.g. ``portageq profile_used default-linux/sparc/sparc64/2004.3
165 gentoo-x86``).
166
167These extensions are assumed during the following specification.
168
138News Item Identities 169News Item Identities
139-------------------- 170--------------------
140 171
141Each news item will have a unique identifier. This identifier will be in the 172Each news item will have a unique identifier. This identifier will be in the
142form ``yyyy-mm-dd-short-name``, where ``yyyy`` is the year (e.g. ``2005``), 173form ``yyyy-mm-dd-short-name``, where ``yyyy`` is the year (e.g. ``2005``),
143``mm`` is the month (``01`` through ``12``) and dd is the day of the month 174``mm`` is the month (``01`` through ``12``) and dd is the day of the month
144(``01`` through ``31``). The ``short-name`` is a very short name describing the 175(``01`` through ``31``). The ``short-name`` is a very short name describing the
145news item (e.g. ``yoursql-updates``), consisting only of the characters ``a-z``, 176news item (e.g. ``yoursql-updates``), consisting only of the characters ``a-z``,
146``0-9`` and ``-`` (hyphen). 177``0-9``, ``+`` (plus), ``-`` (hyphen) and ``_`` (underscore).
147 178
148News Item Directories 179News Item Directories
149--------------------- 180---------------------
150 181
151Each news item will be represented by a directory whose name is the same as the 182Each news item will be represented by a directory whose name is the same as the
153 184
154The directory will contain a file named ``yyyy-mm-dd-short-name.en.txt``, which 185The directory will contain a file named ``yyyy-mm-dd-short-name.en.txt``, which
155contains the text of the news item, in English, in the format described below. 186contains the text of the news item, in English, in the format described below.
156 187
157If a news item is translated, other files named ``yyyy-mm-dd-short-name.xx.txt`` 188If a news item is translated, other files named ``yyyy-mm-dd-short-name.xx.txt``
158(where ``xx`` is the ISO 639 [#iso-639]_ two letter country code) will also be 189(where ``xx`` is the ISO 639 [#iso-639]_ two letter country code, and the date
159provided. However, only the English version of a news item is authoritative. 190remains the same as the original news item) will also be provided. However, only
160This anglocentricity is justified by precedent [#glep-34]_. 191the English version of a news item is authoritative. This anglocentricity is
192justified by precedent [#glep-34]_.
161 193
162News Item Files 194News Item Files
163--------------- 195---------------
164 196
165A news item file is a text file, encoded using UTF-8 [#rfc-3629]_ for 197A news item file is a text file, encoded using UTF-8 [#rfc-3629]_ for
166compatibility with and for the same reasons as existing Gentoo documentation 198compatibility with and for the same reasons as existing Gentoo documentation
167[#docs-policy]_ and the tree [#glep-31]_. 199[#docs-policy]_ and the tree [#glep-31]_.
168 200
169News items should be signed with a detached GPG signature: :: 201News items must be signed with a detached GPG signature.::
170 202
171 gpg --armour --detach-sign ????-??-??-*.??.txt 203 gpg --armour --detach-sign ????-??-??-*.??.txt
204
205This GLEP does not specify the type or strength of signature to be used, nor
206does it discuss how, if at all, a centralised keychain will be provided. These
207issues should be handled as part of the signing policy discussions.
172 208
173A news item file's content will consist of an RFC 822 style header [#rfc-822]_ 209A news item file's content will consist of an RFC 822 style header [#rfc-822]_
174followed by the main body of the message as plain text. This GLEP defines 210followed by the main body of the message as plain text. This GLEP defines
175various optional and mandatory headers. Future GLEPs may propose new headers — 211various optional and mandatory headers. Future GLEPs may propose new headers —
176tools handling these news items must ignore any unrecognised header. 212tools handling these news items must ignore any unrecognised header.
193 229
194``Content-Type:`` 230``Content-Type:``
195 Must be ``text/plain``. Mandatory. 231 Must be ``text/plain``. Mandatory.
196 232
197``Posted:`` 233``Posted:``
198 Date of posting, in ``dd-mmm-yyyy`` format (e.g. 14-Aug-2001) for 234 Date of posting, in ``yyyy-mm-dd`` format (e.g. 2005-12-18) for
199 compatibility with GLEP 1 [#glep-1]_. UTC time in ``hh-mm-ss +0000`` format 235 compatibility with GLEP 45 [#glep-45]_. Translations should use the date
200 may also be included. Mandatory. 236 of the original news item. Mandatory.
201 237
202``Revision:`` 238``Revision:``
203 Initially 1. Incremented every time a non-trivial change is made. Changes 239 Initially 1. Should be incremented every time a change is made to the news
204 which require a re-read of the news item should instead use a new news item 240 item. Changes that require a re-read of the news item (i.e., most changes
241 that are not spelling or formatting related) should instead use a new news
205 file. Mandatory. 242 item. Mandatory.
206 243
207``News-Item-Format:`` 244``News-Item-Format:``
208 Must be ``1.0``. Future revisions to the format may increment the minor 245 Must be ``1.0``. Future revisions to the format may increment the minor
209 number for backwards-compatible changes, or the major number for major 246 number for backwards-compatible changes, or the major number for major
210 changes. 247 changes.
211 248
212The following headers are used for filtering: 249The following headers are used for filtering:
213 250
214``Display-If-Installed:`` 251``Display-If-Installed:``
215 A dependency atom or simple package name (for example, 252 A dependency atom (for example, ``<dev-lang/php-5_alpha`` or
216 ``<dev-lang/php-5_alpha`` or ``net-www/apache``). If the user has the 253 ``net-www/apache``). If the user has the package specified installed from
217 package specified installed, the news item should be displayed. 254 the repository from which the news item was obtained, the news item should
255 be displayed.
218 256
219``Display-If-Keyword:`` 257``Display-If-Keyword:``
220 A keyword [#glep-22]_ name, for example ``mips`` or ``x86-fbsd``. If the 258 A keyword [#glep-22]_ name, for example ``mips`` or ``x86-fbsd``. If the
221 user is on the keyword in question, the news item should be displayed. 259 user is on the keyword in question, the news item should be displayed.
222 260
223``Display-If-Profile:`` 261``Display-If-Profile:``
224 A profile path, for example ``default-linux/sparc/sparc64/server``. Standard 262 A profile path, for example ``default-linux/sparc/sparc64/server``. If the
225 shell GLOB wildcards may be used. If the user is using the exact profile in 263 user is using the exact profile in question, the news item should be
226 question, the news item should be displayed. This header may be used to 264 displayed. This header may be used to replace ``deprecated`` files in the
227 replace ``deprecated`` files in the future. 265 future.
228 266
229.. Note:: When performing package moves, developers must also update any 267.. Note:: When performing package moves, developers must also update any
230 relevant ``Display-If-Installed`` headers in news files. 268 relevant ``Display-If-Installed`` headers in news files.
231 269
232The algorithm used to determine whether a news item is 'relevant' is as 270The algorithm used to determine whether a news item is 'relevant' is as
261 299
262Hyperlinks may be used to refer to further information (for example, an upgrade 300Hyperlinks may be used to refer to further information (for example, an upgrade
263guide). However, the main body of the news item should be descriptive and not 301guide). However, the main body of the news item should be descriptive and not
264simply a "read this link" text. It is assumed that the user will have access to 302simply a "read this link" text. It is assumed that the user will have access to
265a web browser *somewhere*, but not necessarily on the box which is being 303a web browser *somewhere*, but not necessarily on the box which is being
266administrated — this will be the case on may servers and routers, for example. 304administrated — this will be the case on many servers and routers, for example.
267 305
268Example News Item 306Example News Item
269''''''''''''''''' 307'''''''''''''''''
270 308
271`This hypothetical news item`__ could be used for an upgrade to the 309`This hypothetical news item`__ could be used for an upgrade to the
286posted to the ``gentoo-dev`` mailing list and ``Cc:``\ed to ``pr@gentoo.org`` 324posted to the ``gentoo-dev`` mailing list and ``Cc:``\ed to ``pr@gentoo.org``
287(exceptions may be made in exceptional circumstances). Any complaints — for 325(exceptions may be made in exceptional circumstances). Any complaints — for
288example regarding wording, clarity or accuracy — **must** be addressed before 326example regarding wording, clarity or accuracy — **must** be addressed before
289the news item goes live. 327the news item goes live.
290 328
291.. Note:: A previous draft of this GLEP allowed news items to be sent to
292 ``gentoo-core`` instead of ``gentoo-dev``. It is possible that a situation
293 may arise where this will be necessary (for example, a security update which
294 must break backwards compatibility and which cannot be revealed to the public
295 before a given date).
296
297News items must only be for **important** changes that may cause serious upgrade 329News items must only be for **important** changes that may cause serious upgrade
298or compatibility problems. Ordinary upgrade messages and non-critical news items 330or compatibility problems. Ordinary upgrade messages and non-critical news items
299should remain in ``einfo`` notices. The importance of the message to its 331should remain in ``einfo`` notices. The importance of the message to its
300intended audience should be justified with the proposal. 332intended audience should be justified with the proposal.
301 333
319 351
320.. Note:: A previous draft of this GLEP instead used the main ``gentoo-x86`` 352.. Note:: A previous draft of this GLEP instead used the main ``gentoo-x86``
321 tree. This was changed following advice from Infrastructure 353 tree. This was changed following advice from Infrastructure
322 [#ramereth-repo]_. Both solutions have the same end result. 354 [#ramereth-repo]_. Both solutions have the same end result.
323 355
324This repository will contain directories named ``yyyy/mm/``, where ``yyyy`` is 356This repository will contain directories named ``yyyy/``, where ``yyyy`` is
325the current year and ``mm`` is the current month number (01 for January through
32612 for December). This separation will help keep news items more manageable. 357the current year. This separation will help keep news items more manageable.
327 358
328The contents of this repository will automatically be merged with the main rsync 359The contents of this repository will automatically be merged with the main rsync
329tree, placing the items in a ``metadata/news/`` directory. The method used for 360tree, placing the items in a ``metadata/news/`` directory. The method used for
330merging these items is beyond the scope of this GLEP — a similar setup is 361merging these items and the frequency at which it will occur is beyond the scope
331already used for merging GLSAs into the rsync tree. 362of this GLEP; a similar setup is already used for merging GLSAs into the rsync
363tree.
332 364
333The main rsync tree will **not** use the ``yyyy/mm/`` subdirectory layout. 365The main rsync tree will **not** use the ``yyyy/`` subdirectory layout. The
366news item directories will all be immediately under the ``metadata/news/``
367directory.
334 368
335Client Side 369Client Side
336''''''''''' 370'''''''''''
337 371
338Whenever relevant unread news items are found, the package manager will create a 372Whenever relevant unread news items are found, the package manager will create a
339file named ``/var/lib/portage/news/news.unread`` (if it does not already exist) 373file named ``/var/lib/gentoo/news/news-${repoid}.unread`` (if it does not
340and append the news item identifier (eg ``2005-11-01-yoursql-updates``) on a new 374already exist) and append the news item identifier (eg
341line. 375``2005-11-01-yoursql-updates``) on a new line.
342 376
343.. Note:: Future changes to Portage involving support for multiple repositories 377All news item related files should be root owned and in the ``portage`` group
344 may require one news list per repository. Assuming repositories have some 378with the group write (and, for directories, execute) bits set. News files should
345 kind of unique identifier, this file could be named ``news-repoid.unread``. 379be world readable.
346 380
347Notification that new relevant news items will be displayed via the 381Notification that new relevant news items will be displayed via the
348``emerge`` tool in a similar way to the existing "configuration files need 382``emerge`` tool in a similar way to the existing "configuration files need
349updating" messages: 383updating" messages:
350 384
357 391
358* After an ``emerge sync`` 392* After an ``emerge sync``
359* After an ``emerge --pretend`` 393* After an ``emerge --pretend``
360* Before an ``emerge <target>`` (which may also include a red warning message) 394* Before an ``emerge <target>`` (which may also include a red warning message)
361 395
396The package manager does not need to know how to launch the user's choice of
397news client. This is consistent with the way configuration file updates are
398handled.
399
362The package manager may use a timestamp check file to avoid having to process 400The package manager may use a timestamp check file to avoid having to process
363news items unnecessarily. 401news items unnecessarily.
364 402
365The package manager must keep track of news items that have already been added 403The package manager must keep track of news items that have already been added
366to the unread list to avoid repeatedly marking a deleted news item. This could 404to the unread list to avoid repeatedly marking a deleted news item. This could
367be handled via a ``news.skip`` file, but implementation is not specified by this 405be handled via a ``news-${repoid}.skip`` file containing the IDs of news items
368GLEP. 406that have already been added to a ``news-${repoid}.unread`` file, but this
407method is not required by this GLEP.
369 408
370Users who really don't care about news items can use ``rsync_excludes`` to 409Users who really don't care about news items can use ``rsync_excludes`` to
371filter out the ``metadata/news/`` directory. 410filter out the ``metadata/news/`` directory.
372 411
373News Item Clients 412News Item Clients
374----------------- 413-----------------
375 414
376Once a news item is marked for reading, third party tools (or traditional core 415Once a news item is marked for reading, third party tools (or traditional core
377Unix tools) can be used to display and view the news files. 416Unix tools) can be used to display and view the news files.
378 417
379When a news item is read, its name should be removed from the ``news.unread`` 418When a news item is read, its name should be removed from the
380file. News clients may add the name to a ``news.read`` file in the same 419``news-${repoid}.unread`` file. If a news client acts as an interactive reader
420rather than a gateway, it should then add the name to a ``news-${repoid}.read``
381directory with the same file format. 421file in the same directory with the same file format.
382 422
383An ``eselect`` [#eselect]_ module shall be created as the 'suggested' display 423An ``eselect`` [#eselect]_ module shall be created as the 'suggested' display
384tool; other display tools (for example, a news to email forwarder, which would 424tool; other display tools (for example, a news to email forwarder, which would
385be ideal for users who sync on a ``cron``) are left as options for those who 425be ideal for users who sync on a ``cron``) are left as options for those who
386desire them. 426desire them.
409the ``news/`` directory. 449the ``news/`` directory.
410 450
411Reference Implementation 451Reference Implementation
412======================== 452========================
413 453
414Portage Code 454A reference implementation of the required package manager support can be found
415------------ 455in Paludis [#paludis]_, along with a reference newsreader implemented as an
416 456eselect module [#eselect-news]_.
417TODO
418
419Simple ``eselect`` News Client
420------------------------------
421
422TODO Removed until the exact format details are figured out.
423
424Simple News to Mail Forwarder
425-----------------------------
426
427TODO Removed until the exact format details are figured out.
428 457
429Credits 458Credits
430======= 459=======
431 460
432The idea behind notifying users of news updates via Portage comes from Stuart 461The idea behind notifying users of news updates via Portage comes from Stuart
433Herbert [#stuart-blog]_. 462Herbert [#stuart-blog]_.
434 463
435Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear, 464Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear,
436Brian Harring, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec Warner for 465Brian Harring, Marius Mauch, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec
437input. Some of the ideas presented here are theirs, others go completely 466Warner for input. Some of the ideas presented here are theirs, others go
438against their suggestions. 467completely against their suggestions.
439 468
440Example Files 469Example Files
441============= 470=============
442 471
443TODO Removed until the exact format details are figured out. 472`example-news-item.txt <glep-0042-extras/example-news-item.txt>`_
473 An example news item.
444 474
445References 475References
446========== 476==========
447 477
448.. [#bug-11359] Bugzilla Bug 11359 478.. [#bug-11359] Bugzilla Bug 11359
455 http://www.gentoo.org/proj/en/eselect/index.xml 485 http://www.gentoo.org/proj/en/eselect/index.xml
456.. [#forums-glsa] Forums user GLSA, 486.. [#forums-glsa] Forums user GLSA,
457 http://forums.gentoo.org/profile.php?mode=viewprofile&u=55648 487 http://forums.gentoo.org/profile.php?mode=viewprofile&u=55648
458.. [#forums-apache2] Forums thread "Gentoo Apache2 Config Change Idiocy", 488.. [#forums-apache2] Forums thread "Gentoo Apache2 Config Change Idiocy",
459 http://forums.gentoo.org/viewtopic-t-384368.html 489 http://forums.gentoo.org/viewtopic-t-384368.html
460.. [#glep-1] GLEP 1: "GLEP Purpose and Guidelines", Grant Goodyear,
461 http://www.gentoo.org/proj/en/glep/glep-0001.html
462.. [#glep-22] GLEP 22: "New "keyword" system to incorporate various 490.. [#glep-22] GLEP 22: "New "keyword" system to incorporate various
463 userlands/kernels/archs", Grant Goodyear, 491 userlands/kernels/archs", Grant Goodyear,
464 http://www.gentoo.org/proj/en/glep/glep-0022.html 492 http://www.gentoo.org/proj/en/glep/glep-0022.html
465.. [#glep-31] GLEP 31: "Character Sets for Portage Tree Items", Ciaran 493.. [#glep-31] GLEP 31: "Character Sets for Portage Tree Items", Ciaran
466 McCreesh, 494 McCreesh,
468.. [#glep-34] GLEP 34: "Per-Category metadata.xml Files", Ciaran McCreesh, 496.. [#glep-34] GLEP 34: "Per-Category metadata.xml Files", Ciaran McCreesh,
469 http://www.gentoo.org/proj/en/glep/glep-0034.html 497 http://www.gentoo.org/proj/en/glep/glep-0034.html
470.. [#glep-36] GLEP 36: "Subversion/CVS for Gentoo Hosted Projects", Aaron 498.. [#glep-36] GLEP 36: "Subversion/CVS for Gentoo Hosted Projects", Aaron
471 Walker, 499 Walker,
472 http://www.gentoo.org/proj/en/glep/glep-0036.html 500 http://www.gentoo.org/proj/en/glep/glep-0036.html
501.. [#glep-45] GLEP 45: "GLEP date format", Henrik Brix Andersen,
502 http://www.gentoo.org/proj/en/glep/glep-0045.html
473.. [#iso-639] ISO 639 "Code for the representation of names of languages" 503.. [#iso-639] ISO 639 "Code for the representation of names of languages"
474.. [#ramereth-repo] "Re: [gentoo-dev] GLEP ??: Critical News Reporting", Lance 504.. [#ramereth-repo] "Re: [gentoo-dev] GLEP ??: Critical News Reporting", Lance
475 Albertson, 505 Albertson,
476 http://marc.theaimsgroup.com/?l=gentoo-dev&m=113111585907703&w=2 506 http://marc.theaimsgroup.com/?l=gentoo-dev&m=113111585907703&w=2
477.. [#rfc-822] RFC 822 "Standard for the format of ARPA Internet text messages" 507.. [#rfc-822] RFC 822 "Standard for the format of ARPA Internet text messages"
478.. [#rfc-3629] RFC 3629: "UTF-8, a transformation format of ISO 10646" 508.. [#rfc-3629] RFC 3629: "UTF-8, a transformation format of ISO 10646"
479 http://www.ietf.org/rfc/rfc3629.txt 509 http://www.ietf.org/rfc/rfc3629.txt
510.. [#paludis] Paludis homepage, http://paludis.berlios.de
511.. [#eselect-news] news.eselect, http://svn.berlios.de/svnroot/repos/paludis/trunk/eselect/news.eselect
480.. [#stuart-blog] "Favouring an automatic news mechanism", Stuart Herbert, 512.. [#stuart-blog] "Favouring an automatic news mechanism", Stuart Herbert,
481 http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism 513 http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism
482 514
483Copyright 515Copyright
484========= 516=========

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.14

  ViewVC Help
Powered by ViewVC 1.1.20