Hello,
the developers of an app I'm packaging, denemo (www.denemo.org) do not
use (it is there, but not updated since months) the file ChangeLog.
However, they do keep a list of changes, which they published, for the
last release, in their site and on the mailing list, and which content
would be
Hi,
2009/11/5 Pietro Battiston too...@email.it:
Hello,
the developers of an app I'm packaging, denemo (www.denemo.org) do not
use (it is there, but not updated since months) the file ChangeLog.
However, they do keep a list of changes, which they published, for the
last release, in their
Il giorno gio, 05/11/2009 alle 23.20 +0100, Sandro Tosi ha scritto:
Hi,
2009/11/5 Pietro Battiston too...@email.it:
Hello,
the developers of an app I'm packaging, denemo (www.denemo.org) do not
use (it is there, but not updated since months) the file ChangeLog.
However, they do keep
Hi,
Sandro Tosi wrote:
P.P.S: I'm taking care of this package since few months... under
previous maintainer, the upstream ChangeLog was still updated
That's nicer, but I don't think it's worth a hunk in diff.gz (either
as direct change or patch) for this.
What’s stopping one from shipping
Pietro Battiston too...@email.it writes:
Do you suggest me to:
- patch the changelog/introduce a new one, and then install it, or
- in debian/changelog, after New upstream release, list all of those
changes?
I always summarize major changes in a new upstream release in
debian/changelog
Russ Allbery r...@debian.org writes:
I always summarize major changes in a new upstream release in
debian/changelog whether upstream provides its own changelog or not.
It seems polite and I know as a user it makes debian/changelog more
useful to me than a bunch of bare New upstream release
6 matches
Mail list logo
