On Sun, Jan 10, 2010 at 10:58:01PM +0800, Paul Wise wrote:
[...]
If you use a version control system, there are cvs2cl, svn2cl, git2cl
and probably other scripts to convert your commit messages into
GNU-style ChangeLog files, no need to reinvent the wheel here.
[...]
I did anyway--using
On Sun, 2010-01-10 at 14:00 +, Seger, Mark wrote:
Is there any standard (or desired format). Since I intend to include
both my release notes and an automatically generated changelog, it
should be pretty easy to create the log headers in any format people
would like to see.
As an
I fear I may be opening a can or worms but also feel I need to ask. I'm trying
to add a changelog to my collectl package and as I don't currently have one, I
currently have a file containing release notes, I thought I'd look to see what
others are doing as my plan is to just write a perl
I assume you are talking about the upstream ChangeLog rather than
debian/changelog.
The only standard I am aware of for that is the one described in the
GNU coding standards document[1]. Many upstreams completely ignore it
and the recommended file naming (ChangeLog not CHANGES.TXT or one of
the
Il giorno dom, 10/01/2010 alle 22.58 +0800, Paul Wise ha scritto:
I assume you are talking about the upstream ChangeLog rather than
debian/changelog.
The only standard I am aware of for that is the one described in the
GNU coding standards document[1].
The suggested document doesn't mention
Some additional comments from me that may or may not be worth reading.
Paul Wise wrote:
The GNU coding standards document doesn't recommend any specific
format for NEWS files.
Right -- the format is (and has always been) free-form; it's usually a
nested list suitable for Emacs' outline-mode.
Paul Wise p...@debian.org writes:
Please be aware of the difference between NEWS files and ChangeLog files
in the GNU coding standards document. Most upstreams completely ignore
this difference. GNU NEWS[3] files are a list of user-visible changes
for each release. The GNU coding standards
Paul Wise p...@debian.org writes:
If you use a version control system, there are cvs2cl, svn2cl, git2cl
and probably other scripts to convert your commit messages into
GNU-style ChangeLog files, no need to reinvent the wheel here.
For Bazaar, this is an option to the ‘log’ command:
bzr
Russ Allbery r...@debian.org writes:
I think NEWS is far and away the more useful of the two files. Usually
the full changelog has an overwhelming amount of detail and isn't
horribly useful at answering users' questions.
How would you relate this valuation against the Lintian checks? Should
Ben Finney ben+deb...@benfinney.id.au writes:
Russ Allbery r...@debian.org writes:
All of the packages for which I'm both upstream and the Debian packager
have no traditional ChangeLog file, only NEWS, and install the upstream
NEWS file as /usr/share/doc/package/changelog.gz.
Perhaps that
On Mon, Jan 11, 2010 at 6:02 AM, Russ Allbery r...@debian.org wrote:
There's an open Policy bug about this, which is where it should probably
be discussed. When packaging other people's software, I install the
upstream ChangeLog as changelog.gz and NEWS as NEWS.gz.
For some packages where
Paul Wise p...@debian.org writes:
On Mon, Jan 11, 2010 at 6:02 AM, Russ Allbery r...@debian.org wrote:
There's an open Policy bug about this, which is where it should probably
be discussed. When packaging other people's software, I install the
upstream ChangeLog as changelog.gz and NEWS as
12 matches
Mail list logo
