Re: tagging 2.13.1

2009-06-09 Thread Han-Wen Nienhuys
On Tue, Jun 9, 2009 at 7:47 AM, Francisco Vila wrote: > Along with tagging+releasing, wouldn't be great to know which commit > does a release come from, just making the build process to write it > down in a README file? Nowadays, tagging is a manual event that can be > forgotten (and it is). No, i

Re: tagging 2.13.1

2009-06-09 Thread Francisco Vila
Along with tagging+releasing, wouldn't be great to know which commit does a release come from, just making the build process to write it down in a README file? Nowadays, tagging is a manual event that can be forgotten (and it is). Also, it would be useful to know what commit has a webpage been pro

Re: tagging 2.13.1

2009-06-07 Thread Han-Wen Nienhuys
939d350c114854ce026e31eddb07abf73be6840f refs/tags/release/2.13.1-1 $ tags/release/2.13.1-1|head tag release/2.13.1-1 Tagger: Han-Wen Nienhuys Date: Mon Jun 1 11:30:54 2009 -0300 commit 457b7a93eec7afdab5c76e99f3f4c151047e3bdb Author: Reinhold Kainhofer Date: Sun May 24 17:03:50 2009 +0200

Re: tagging 2.13.1

2009-06-07 Thread Graham Percival
On Sun, Jun 07, 2009 at 08:07:43PM +0100, Neil Puttock wrote: > 2009/6/7 Graham Percival : > > > I did: > >  git tag release/2.13.1 0ac...86a > > and I can see the tag in my own gitk, but when I push, it doesn't > > update the list of tags on the web-git page.  Anybody know what's > > wrong? > >

Re: tagging 2.13.1

2009-06-07 Thread Neil Puttock
2009/6/7 Graham Percival : > I did: >  git tag release/2.13.1 0ac...86a > and I can see the tag in my own gitk, but when I push, it doesn't > update the list of tags on the web-git page.  Anybody know what's > wrong? Did you do `git push --tags' too? Regards, Neil _

Re: tagging 2.13.1

2009-06-07 Thread Graham Percival
On Sun, Jun 07, 2009 at 06:52:49PM +0100, Neil Puttock wrote: > 2009/6/7 Mark Polesky : > > > Reinhold Kainhofer > > Better detection which characters need to be quoted... > > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=0ac32e91fab38b860ad951b8f0cd4700f79ba86a > > This is the re

Re: tagging 2.13.1

2009-06-07 Thread Neil Puttock
2009/6/7 Mark Polesky : > Reinhold Kainhofer > Better detection which characters need to be quoted... > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=0ac32e91fab38b860ad951b8f0cd4700f79ba86a This is the release commit. If you look at the regression test results, you'll see it lis

Re: tagging 2.13.1

2009-06-06 Thread Mark Polesky
Patrick McCarty wrote: > That is the commit that bumped the VERSION file. > Graham wants to know which commit 2.13.1 is based on. > For example, 2.13.0 was based on this commit: > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=37a38d4a18943041e4d3623fb3996279f40df290 Ah, I see. We

Re: tagging 2.13.1

2009-06-06 Thread Patrick McCarty
On Sat, Jun 6, 2009 at 3:47 PM, Mark Polesky wrote: > >> Does anybody remember which commit was used for 2.13.1?  We should > >> tag that. > > Isn't it this one? > > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=e49c69e6d1e507f60348fa168332175ec6d42b0a That is the commit that bumpe

Re: tagging 2.13.1

2009-06-06 Thread Mark Polesky
> Does anybody remember which commit was used for 2.13.1? We should > tag that. Isn't it this one? http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=e49c69e6d1e507f60348fa168332175ec6d42b0a ___ lilypond-devel mailing list lily

tagging 2.13.1

2009-06-06 Thread Graham Percival
Does anybody remember which commit was used for 2.13.1? We should tag that. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel