| 1 |
On 27 October 2011 06:33, Bruno <bonbons67@××××××××.lu> wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> Is there some guideline about old entries in the ChangeLog? |
| 5 |
> |
| 6 |
> Over the past months ChangeLogs represent a big part of the tree, some |
| 7 |
> of them being pretty big and going back many changes (hundreds of them) |
| 8 |
> and years (even for actively maintained ebuilds). |
| 9 |
> |
| 10 |
> |
| 11 |
A lot of the older changelog entries also tend to be less normal, and some |
| 12 |
long changelogs are so a-typical its virtually impossible to parse them with |
| 13 |
machine code. |
| 14 |
|
| 15 |
I know its probably not a big priority for most people, but if changelogs |
| 16 |
can retain consistency so that the only part which is inconsistent is the |
| 17 |
messages themselves. |
| 18 |
|
| 19 |
I saw the --echangelog parameter turn up sometime this week and I haven't |
| 20 |
played with it for fear of subtle inconsistencies with the form produced by |
| 21 |
the echangelog client. |
| 22 |
|
| 23 |
( I've been hacking on various tools to parse/normalise changelogs myself, |
| 24 |
but it got overwhelming and I got sidetracked ) |
| 25 |
|
| 26 |
-- |
| 27 |
Kent |
| 28 |
|
| 29 |
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 ) |
| 30 |
for ( 9,8,0,7,1,6,5,4,3,2 );" |
| 31 |
|
| 32 |
http://kent-fredric.fox.geek.nz |
Archives