On Fri, 04 Jun 2004 18:48:31 +0200 Erik Sandberg
<[EMAIL PROTECTED]> wrote:
> > Just having recently noticed that the closing notification of a bug
> > is to be written in lilypond/ChangeLog, I have to say that you are doing
> > well!
>
> This is a _very_ good point... So, until we find a good re
On Friday 04 June 2004 18.04, Heikki Johannes Junes wrote:
> On Fri, 4 Jun 2004, Erik Sandberg wrote:
> > And the interest of closed bugs has made me decide to keep closed bugs in
> > the future, probably in the lilypond-bugs/closed/ directory. This would
> > work even better for this purpose; just
Fri, 4 Jun 2004 14:39:04 +0200, Erik a dit :
> btw, is there an automated way to create changelogs in conjunction with
> writing commit messages in CVS? All changelogs look quite standardised; so i
> just suppose the process is automatised somehow.
> (if I have to do something manually, th
On Fri, 4 Jun 2004, Erik Sandberg wrote:
>
> And the interest of closed bugs has made me decide to keep closed bugs in the
> future, probably in the lilypond-bugs/closed/ directory. This would work even
> better for this purpose; just browse that directory for the bug.
>
Just having recently notic
On Wednesday 02 June 2004 00.13, Heikki Johannes Junes wrote:
> > Personally, I do not think that there will be a big public interest in
> > the history of lilypond bugs. What I believe could be interesting, is the
> > set of open bugs, and the set of very recently closed bugs. I.e. what
> > will b
> Personally, I do not think that there will be a big public interest in
> the history of lilypond bugs. What I believe could be interesting, is the
> set of open bugs, and the set of very recently closed bugs. I.e. what will be
> in CVS with my latest suggestion.
I disagree. Think you were a fun
> Since all developers should have the latest lilypond versions, they
> will not add any bugs to the database, that don't exist in the
> latest lilypond version. Thus there is no risk of reporting bugs
> the same bugs again and again.
I don't insist on a ChangeLog if you think that you can manag
On Tuesday 01 June 2004 01.27, Werner LEMBERG wrote:
> > > I strongly suggest to start a ChangeLog file to document changes
> > > in the repository, mainly to avoid reporting the same errors again
> > > and again.
> >
> > I think there's a simpler solution than using a ChangeLog.
> >
> > One is to
> > I strongly suggest to start a ChangeLog file to document changes
> > in the repository, mainly to avoid reporting the same errors again
> > and again.
>
> I think there's a simpler solution than using a ChangeLog.
>
> One is to use the convention that bugs are removed only directly
> after t
On Saturday 15 May 2004 16.53, Werner LEMBERG wrote:
> Right now I've seen that some bug reports have been removed from
> lily-bugs.
>
> I strongly suggest to start a ChangeLog file to document changes in
> the repository, mainly to avoid reporting the same errors again and
> again.
I think there'
Right now I've seen that some bug reports have been removed from
lily-bugs.
I strongly suggest to start a ChangeLog file to document changes in
the repository, mainly to avoid reporting the same errors again and
again.
Werner
___
lilypond-devel
11 matches
Mail list logo
