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

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

  ViewVC Help
Powered by ViewVC 1.1.20