Re: lilypond development moved

2006-11-13 Thread Jan Nieuwenhuizen
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Proposal: > > * put ChangeLog into Documentation/misc/ > * for each release, do a > >git log release/2.11.0.. > Changes Hmm, why not use a vamped-up version of buildscripts/update-git-update-changelog to generate a more informative and more h

Re: lilypond development moved

2006-11-13 Thread Han-Wen Nienhuys
Werner LEMBERG escreveu: 3), are ChangeLog entries still necessary? No, don't write ChangeLog entries anymore. Just put all the information in the commit log. Hmm, hmm. Contrary to the Linux kernel I urgently ask to make a dump of the commit log part of the final tarball. I don't mind pack

Re: lilypond development moved

2006-11-13 Thread Werner LEMBERG
> > 3), are ChangeLog entries still necessary? > > > > No, don't write ChangeLog entries anymore. Just put all the > information in the commit log. Hmm, hmm. Contrary to the Linux kernel I urgently ask to make a dump of the commit log part of the final tarball. Werner ___

Re: lilypond development moved

2006-11-13 Thread Han-Wen Nienhuys
John Mandereau escreveu: Han-Wen Nienhuys wrote: Hello all, we've recently switched to GIT for version control. As a temporary measure, we had a repository at repo.or.cz. However, in collaboration with the savannah hackers, I've now successfully set up a git repository at savannah. Check i

Re: lilypond development moved

2006-11-12 Thread John Mandereau
Han-Wen Nienhuys wrote: > > Hello all, > > we've recently switched to GIT for version control. As a temporary > measure, we had a repository at repo.or.cz. However, in collaboration > with the savannah hackers, I've now successfully set up a git repository > at savannah. Check it out at > >