1 |
suggestion: |
2 |
stop keeping ChangeLog files in CVS and instead, let them be generated |
3 |
automagically by the cvs server using the last <arbitrary number> of commit |
4 |
messages. if you really want to keep a commit message out of the changelog, |
5 |
then we come up with a simple policy of prefixing the message with a period |
6 |
(to keep it hidden :P). |
7 |
|
8 |
logic: |
9 |
- i'm lazy |
10 |
- i hate typing the samething twice (yes, bash scripting with echangelog can |
11 |
kind of take care of this) ... it doesnt handle if you want to use different |
12 |
commit messages for different files |
13 |
- shrinks ChangeLog size for packages which have been around a very long time |
14 |
- forces cvs log messages to actually be worthwhile to read and makes |
15 |
browsing cvs history much nicer (it's very easy to look at the differences |
16 |
between two files and match up a good commit message rather than trying to |
17 |
figure out what message in the ChangeLog goes with it, assuming there is one) |
18 |
- easily standardize ChangeLog format wrt to header, copyrights, licensing, |
19 |
message formatting, name/date format |
20 |
- generate dates in UTC down to the second rather than having devs hand type |
21 |
them in their local timezone for just the current day |
22 |
- maybe some other things i havent thought of |
23 |
- i'm lazy |
24 |
-mike |
25 |
-- |
26 |
gentoo-dev@g.o mailing list |