1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
| I don't think this is appropriate for -dev, but since you started it |
5 |
| here, I'm going to comment. |
6 |
|
7 |
Oh, so is this one of those "98% of the discussions held on -core are |
8 |
not interesting"? |
9 |
|
10 |
|Why are you doing this? Sanctioned or not, |
11 |
| the "old" way was never enforced, and not clearly stated as policy in |
12 |
| the developer's handbook. Also, many prefer the new way. Let's |
13 |
| consider this: |
14 |
|
15 |
What about |
16 |
~ |
17 |
*************************************************************************** |
18 |
~ THIS IS IMPORTANT: The ChangeLog format is a *chronological* account |
19 |
~ of all changes made to a set of ebuilds. That means that the most |
20 |
recent ChangeLog entry *always* goes at the top of the file. More |
21 |
~ explanation below. |
22 |
*************************************************************************** |
23 |
|
24 |
I normally wouldn't care, but since the topic was wildly discussed just |
25 |
a few days ago and writing proper ChangeLogs was mentioned as a must. |
26 |
|
27 |
//Daniel Armyr |
28 |
- -- |
29 |
========================================= |
30 |
daniel.armyr@××××.se f00-dar@×××××.se |
31 |
|
32 |
C118 KEVII Hall |
33 |
1A Kent Ridge Rd S.119224 |
34 |
Singapore PGP@×××××××.edu |
35 |
========================================= |
36 |
-----BEGIN PGP SIGNATURE----- |
37 |
Version: GnuPG v1.2.1 (GNU/Linux) |
38 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
39 |
|
40 |
iD8DBQE+rHRMhxtTUWLs2lERAtNQAKCkFB01qL9AJaEDPVoxjtm2ZXTQ4wCfXVdi |
41 |
FZmAQTPjdMHPOlCy+iWcMDY= |
42 |
=YH6f |
43 |
-----END PGP SIGNATURE----- |
44 |
|
45 |
|
46 |
-- |
47 |
gentoo-dev@g.o mailing list |