[prev in list] [next in list] [prev in thread] [next in thread] 

List:       vcs-pkg
Subject:    Re: autogenerating debian/NEWS (was: TopGit: Is there still a need
From:       James Vega <jamessan () debian ! org>
Date:       2009-05-05 20:19:20
Message-ID: 20090505201920.GG3732 () jamessan ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tue, May 05, 2009 at 09:59:01PM +0200, martin f krafft wrote:
> also sprach James Vega <jamessan@debian.org> [2009.05.05.2135 +0200]:
> > Files that are purely a result of the final integration (like
> > debian/changelog, debian/NEWS, and debian/patches/*) only exist in the
> > integration branch.  This provides a clean separation between the
> > changes I'm actively making to handle the debianization of the upstream
> > source and the changes that are only being made in the process of an
> > upload.
> 
> How do you generate debian/NEWS?

With `dch --news' and my fingers. :) I don't (yet) have either
debian/changelog or debian/NEWS generated and I'm not sure that'd be
easy for the latter.  It just doesn't make sense to me to have either of
these files on branches other than the ones from which releases are cut.

I'm more comfortable with collating the commit logs into
debian/changelog using a tool like git-dch and then massaging the data
into what's relevant for a user-facing changelog.

I guess one could use specific commit log formatting and automate
pulling that metadata out into the debian/NEWS and debian/changelog
entries, but I haven't given much thought to it.

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jamessan@debian.org>

["signature.asc" (application/pgp-signature)]

_______________________________________________
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss


[prev in list] [next in list] [prev in thread] [next in thread]