1 |
On Sunday 06 May 2007 3:31:32 pm Ciaran McCreesh wrote: |
2 |
> On Sun, 6 May 2007 15:26:06 -0400 |
3 |
> |
4 |
> Dan Meltzer <hydrogen@×××××××××××××××××.com> wrote: |
5 |
> > On Sunday 06 May 2007 2:47:22 pm Ciaran McCreesh wrote: |
6 |
> > > On Sun, 6 May 2007 20:41:24 +0200 |
7 |
> > > |
8 |
> > > expose@×××××××××××.net wrote: |
9 |
> > > > Ciaran, if you where a bit more verbose you could save time. |
10 |
> > > |
11 |
> > > If people read the rest of the thread and the GLEP we'd all save a |
12 |
> > > lot more, and if people also tried out a reference implementation |
13 |
> > > then none of these threads would need more than about three posts... |
14 |
> > |
15 |
> > You say this, but every time someone quotes a relevant refuting part |
16 |
> > of the GLEP, you ignore it. |
17 |
> > |
18 |
> > Try this one: |
19 |
> |
20 |
> Read the rest of the threads. I've already answered that several times. |
21 |
|
22 |
No, I've read the other threads. You've not explained how this is a critical |
23 |
update that requires a news item. You've said repeatedly in response to |
24 |
related questions that your experience with news for one package in one |
25 |
overlay used by a small subset of users that uses said package recieved good |
26 |
feedback, and that they would like to be informed of changes in the future. |
27 |
You were informed that elog can do just that, and you said repeatedly that |
28 |
elog is not sufficient because its not loggged by default. You could easily |
29 |
make elog logged by default in paludis, and that would achieve the same |
30 |
result as a news item. What did I forget? |
31 |
-- |
32 |
gentoo-dev@g.o mailing list |