| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 31/10/12 11:26 AM, Alexis Ballier wrote: |
| 5 |
> On Tue, 30 Oct 2012 18:39:44 -0600 Ryan Hill |
| 6 |
> <dirtyepic@g.o> wrote: [...] |
| 7 |
>>> The file is pointless if not everyone is using it. I've |
| 8 |
>>> offered to remove the file before, and I'm reoffering to do so |
| 9 |
>>> now. |
| 10 |
>> |
| 11 |
>> It's pointy enough for most uses. Let's keep it that way. |
| 12 |
> |
| 13 |
> I would like to know what are those uses. Here are my thoughts |
| 14 |
> about changelogs: |
| 15 |
> |
| 16 |
> We have cvs logs, cvsweb, etc. So what is the value added from |
| 17 |
> changelogs? Well, those logs are per-file as far as I know, and |
| 18 |
> since a new version of a package means a new .ebuild file, keeping |
| 19 |
> track of changes to packages is painful without a changelog which |
| 20 |
> is global to the whole package. Even if we have all the needed |
| 21 |
> information in the cvs log, changelogs for packages are definitely |
| 22 |
> useful. Now for eclasses the situation is different: I want to |
| 23 |
> know what has recently changed in foo.eclass, what is the fastest |
| 24 |
> way? Search through a changelog file with dozens of absolutely |
| 25 |
> unrelated information, or run cvs log/go to sources.gentoo.org ? I |
| 26 |
> tend to do the latter and find eclass changelogs completely |
| 27 |
> useless. |
| 28 |
> |
| 29 |
|
| 30 |
Cool, you do, that's great. This doesn't mean others don't use a |
| 31 |
different process tho, and since it *IS* there and is *SUPPOSED* to be |
| 32 |
filled, and it really doesn't hurt to run 'echangelog "${msg}" && cvs |
| 33 |
ci -m "${msg}"' , why not do it? |
| 34 |
|
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 37 |
|
| 38 |
iF4EAREIAAYFAlCRRU0ACgkQ2ugaI38ACPCobwD+LZvXFPyfsGZ+484wnkv6fk8L |
| 39 |
oBazGyjti3n2nNAkM8IA/A5IvVNyOnd6U9lVH1B2dRA2HB1+i8Hac1aAKvs/EPF1 |
| 40 |
=F5eR |
| 41 |
-----END PGP SIGNATURE----- |
Archives