| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi foser, |
| 5 |
|
| 6 |
>>>alpha++ |
| 7 |
>>once again, alpha++ |
| 8 |
> It's not a vote, it's a discussion. You guys--. |
| 9 |
^^^Yeah, this proofs your ability to discuss very well... |
| 10 |
|
| 11 |
> As vapier indicates he's the whole reason this ever became a problem. He |
| 12 |
> was the one who started arbitrarily ordering keywords around creating a |
| 13 |
> keywords mess for people who did depend on order to perform tasks. I |
| 14 |
> guess the lesson here is if you just do things 'your way' (wr/l)ong |
| 15 |
> enough, people pick it up and it spreads. |
| 16 |
Chris pointed out that there are developer who switched their arch at |
| 17 |
least once, |
| 18 |
and other who don't have access to the same arch all the time (x86 on |
| 19 |
work, $arch at home). So the point is: even without alpha ordering, you |
| 20 |
_cannot rely_ on the precious 'implicit information' you want to store |
| 21 |
in keyword ordering. And to quote on of my teachers: unreliable |
| 22 |
information is worse than no information at all. |
| 23 |
|
| 24 |
> The point is that with his reordering implicit information was lost for |
| 25 |
> no particular purpose. There was no added value in ordering keywords, |
| 26 |
No, you're wrong here: you couldn't rely on it from the beginning, so |
| 27 |
nothing was lost... |
| 28 |
|
| 29 |
Danny |
| 30 |
- -- |
| 31 |
Danny van Dyk <kugelfang@g.o> |
| 32 |
Gentoo/AMD64 Project, Gentoo Scientific Project |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 35 |
|
| 36 |
iD8DBQFCqGBxaVNL8NrtU6IRAq9HAJ9cTSPI1q4ld8xWSIJjQkkhWWmjWgCfcw3S |
| 37 |
YtOcIeTW9ERUwa7k++ct8UA= |
| 38 |
=quF1 |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives