| 1 |
On Sunday 06 May 2007 2:47:22 pm Ciaran McCreesh wrote: |
| 2 |
> On Sun, 6 May 2007 20:41:24 +0200 |
| 3 |
> |
| 4 |
> expose@×××××××××××.net wrote: |
| 5 |
> > Ciaran, if you where a bit more verbose you could save time. |
| 6 |
> |
| 7 |
> If people read the rest of the thread and the GLEP we'd all save a lot |
| 8 |
> more, and if people also tried out a reference implementation then none |
| 9 |
> of these threads would need more than about three posts... |
| 10 |
|
| 11 |
You say this, but every time someone quotes a relevant refuting part of the |
| 12 |
GLEP, you ignore it. |
| 13 |
|
| 14 |
Try this one: |
| 15 |
|
| 16 |
"News items must only be for important changes that may cause serious upgrade |
| 17 |
or compatibility problems. Ordinary upgrade messages and non-critical news |
| 18 |
items should remain in einfo notices. The importance of the message to its |
| 19 |
intended audience should be justified with the proposal." |
| 20 |
|
| 21 |
Now, the news item in this thread seems relevant to that. WIthout doing what |
| 22 |
it says one will have a fairly major headache on their hands after upgrading. |
| 23 |
|
| 24 |
The other example news item does not fit these criteria, there will be no |
| 25 |
major headache, there will be a warning that can be quickly fixed. |
| 26 |
> |
| 27 |
> > Things like this happened at least a few times in the recent |
| 28 |
> > discussion. I, for instance, still wait for an answer to the question |
| 29 |
> > "How?" concerning you "answer" |
| 30 |
> > |
| 31 |
> > > The 'eselect news' module that ships with Paludis solves that |
| 32 |
> > > problem. |
| 33 |
> > |
| 34 |
> > which I'd still like to hear. |
| 35 |
> |
| 36 |
> Perhaps you should... you know... try it. Then you'd be able to provide |
| 37 |
> much more useful input to the discussion. |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives