Hi,
On Di, 24 Apr 2012, Ben Finney wrote:
> To say it more plainly: Modifying previous changelog entries, while not
> prohibited, does break an implicit user expectation. I think that
> expectation is reasonable to an extent, and breaking it is costly to the
> same extent.
But there are good reas
Russ Allbery writes:
> Ben Finney writes:
> > [modifying previous changelog entries] breaks the entirely
> > reasonable expectation: that a changelog only ever accumulates
> > entries for the latest release, and nothing in earlier releases has
> > changed since the last time the recipient read t
Tomasz Muras writes:
> On 04/22/2012 02:48 PM, Bernhard R. Link wrote:
>> * Arno Töll [120421 11:51]:
>>> The whole point of a changelog is a time dependent frozen point of view
>>> at your package. Once you released a version of a package, you should
>>> consider it untouchable
>>
>> I strongly
On 04/22/2012 02:48 PM, Bernhard R. Link wrote:
* Arno Töll [120421 11:51]:
The whole point of a changelog is a time dependent frozen point of view
at your package. Once you released a version of a package, you should
consider it untouchable
I strongly disagree. First of all, a changelog is t
* Arno Töll [120421 11:51]:
> The whole point of a changelog is a time dependent frozen point of view
> at your package. Once you released a version of a package, you should
> consider it untouchable
I strongly disagree. First of all, a changelog is there to see what has
changed when, i.e. it is
Ben Finney writes:
> Charles Plessy writes:
>> are there concrete problems caused by modifying previous changelog
>> entries ?
> Doing that breaks the entirely reasonable expectation: that a changelog
> only ever accumulates entries for the latest release, and nothing in
> earlier releases has
Le Sun, Apr 22, 2012 at 12:22:43PM +1000, Ben Finney a écrit :
> Charles Plessy writes:
>
> > are there concrete problems caused by modifying previous changelog
> > entries ?
>
> Doing that breaks the entirely reasonable expectation: that a changelog
> only ever accumulates entries for the lates
Charles Plessy writes:
> are there concrete problems caused by modifying previous changelog
> entries ?
Doing that breaks the entirely reasonable expectation: that a changelog
only ever accumulates entries for the latest release, and nothing in
earlier releases has changed since the last time th
On 21.04.2012 09:35, Charles Plessy wrote:
> are there concrete problems caused by modifying previous changelog entries ?
> I
> do it from time to time, of course not when the diff has to be carefully
> inspected by others as it would be a distraction, and I have not found it
> causing breakages.
>
> * Do not modify previous changelog entries, especially not in NMUs.
Hi all,
are there concrete problems caused by modifying previous changelog entries ? I
do it from time to time, of course not when the diff has to be carefully
inspected by others as it would be a distraction, and I have no
10 matches
Mail list logo
