1 |
On Sat, Apr 30, 2011 at 02:42:08PM +0100, Markos Chandras wrote: |
2 |
> On Sat, Apr 30, 2011 at 12:02:35PM +0300, Samuli Suominen wrote: |
3 |
> > On 04/30/2011 11:46 AM, Petteri Räty wrote: |
4 |
> > > http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/index.html |
5 |
> > > |
6 |
> > > There doesn't seem to be a common opinion on what the policy for |
7 |
> > > ChangeLog entries is. See: |
8 |
> > > |
9 |
> > > http://archives.gentoo.org/gentoo-dev/msg_f829da2375f1ceab766a800913cc4998.xml |
10 |
> > > |
11 |
> > > I propose a simple new text: "Every commit should have an entry in |
12 |
> > > ChangeLog." If we eventually autogenerate them from git logs this would |
13 |
> > > happen any way (unless some kind of filtering system is in the middle) |
14 |
> > > so we could already start now. I think it's better to have more than |
15 |
> > > less information available to users. |
16 |
> > > |
17 |
> > > Regards, |
18 |
> > > Petteri |
19 |
> > > |
20 |
> > |
21 |
> > "Every new file, and modification to existing file should have an entry |
22 |
> > in ChangeLog." to skip the proper ChangeLog-less removals. |
23 |
> > |
24 |
> I am actually with Samuli on this. Unless there is a particular reason |
25 |
> for removing a package, I don't see any point of documenting this change anywhere. |
26 |
> What difference would it make to you if you see an entry " -foo-1.0 |
27 |
> old". It makes absolutely no sense. |
28 |
|
29 |
There are times when you need to know where a version went. That alone |
30 |
is enough to warrant updating the ChangeLog. |
31 |
|
32 |
Having to check a second place through a slow interface sucks :) |
33 |
|
34 |
-- |
35 |
Alex Alexander | wired |
36 |
+ Gentoo Linux Developer |
37 |
++ www.linuxized.com |