Re: cheese changelog



On Di, 2009-04-21 at 19:19 +0200, Filippo Argiolas wrote:
> On Tue, Apr 21, 2009 at 3:51 PM, daniel g. siegel <dgsiegel gnome org> wrote:
> > On Di, 2009-04-21 at 15:34 +0200, Filippo Argiolas wrote:
> >> On Tue, Apr 21, 2009 at 3:26 PM, Patryk Zawadzki <patrys pld-linux org> wrote:
> >> >>> It would be perfectly fine to just generate ChangeLog from git history
> >> >>> when packaging a release. No need to keep it under version control.
> >> >> is there any specific format you would need?
> >> >
> >> > Usual stuff: date, name, description, files affected?
> >>
> >> As far I as I know Behdad is working on integrating the ChangeLog
> >> macro directly into gnome-common as soon as the git module is fixed.
> >> As he wrote the current rule that can be found on l.g.o and that
> >> several modules are already using the format will probably stay that
> >> one (git log --stat).
> >
> > so, should we wait for the work being finished?
> 
> Sure, we can wait, not that we're going to release anything soon.
> I'd say for now we can just:
> - git mv ChangeLog ChangeLog.pre-git
> - add a new ChangeLog with the following

ok, go for it!

> 
> 2009-04-21  bla bla <blabla bla>
> 
>        * *: The ChangeLog is auto-generated when releasing. If you
>        are seeing this, use 'git log' for a detailed list of changes.

i think, just the message is enough (i.e. without date, name and mail
address)

daniel

> 
> > another thing: on the ddl-list, some guys proposed some other format.
> > might be worth a look
> 
> Anything is good for me as long as I'm never going to read it :)
> Seriously, would be great to have a single shared format for
> autogenerated ChangeLog across all modules, so the one that will go in
> gnome-common should be fine.
> 
> Filippo
-- 
this mail was sent using 100% recycled electrons
================================================
daniel g. siegel <dgsiegel gmail com>
http://home.cs.tum.edu/~siegel
gnupg key id: 0x6EEC9E62
fingerprint: DE5B 1F64 9034 1FB6 E120 DE10 268D AFD5 6EEC 9E62
encrypted email preferred

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]