2013/4/7 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>> yeah, i do that too (had 20+ builds at one point of time).
>
> A quick count shows I've got about 77 builds on my Windows box...
Whoah! You've beaten me, sir! ;)
Janek
___
l
- Original Message -
From: "Janek Warchoł"
To: "David Kastrup"
Cc: "Phil Holmes" ; "LilyPond Users"
Sent: Sunday, April 07, 2013 8:47 PM
Subject: Re: tracking lilypond builds with git
yeah, i do that too (had 20+ builds at one point of tim
Hi,
2013/4/7 Phil Holmes :
> - Original Message - From: "Janek Warchoł"
>> However, i'd be very interested in seeing a solution for this (i.e.
>> how to efficiently store lily executables in a repository).
>
> Not convinced it's worth doing. The point of a repository is the ability to
> t
"Phil Holmes" writes:
> Not convinced it's worth doing. The point of a repository is the
> ability to track change.
Well, the ability to save storage place is also nice. And you can still
do git bisect...
> If that's of no value (and it isn't with binaries) then you might as
> well just have
- Original Message -
From: "Janek Warchoł"
To: "David Kastrup"
Cc: "LilyPond Users"
Sent: Sunday, April 07, 2013 4:11 PM
Subject: tracking lilypond builds with git (was: lilypond source and
musicsheet database)
Hi,
2013/4/7 David Kastrup :
Jan
Hi,
2013/4/7 David Kastrup :
> Janek Warchoł writes:
>
>> 2013/4/7 David Kastrup :
>>> Packing actual executables could possibly also work with reasonable
>>> overhead.
>>>
>>> There would be an advantage to a repository storing _complete_ compiled
>>> versions of LilyPond: it would make "git bis
