Thanks Joseph for pointing me to git checkouts..it works for me.
On Sun, Apr 7, 2013 at 7:42 PM, pls wrote:
> On 07.04.2013, at 19:29, Joseph Rushton Wakeling <
> joseph.wakel...@webdrake.net> wrote:
>
> On 04/07/2013 06:51 PM, Stjepan Horvat wrote:
>
> I realy like git too..Once i tried to make
On 07.04.2013, at 19:29, Joseph Rushton Wakeling
wrote:
> On 04/07/2013 06:51 PM, Stjepan Horvat wrote:
>> I realy like git too..Once i tried to make my own git server on my private
>> web-server so when i finish the work i can send the customer his pdf folder
>> link..but..that didnt work becou
On 04/07/2013 06:51 PM, Stjepan Horvat wrote:
> I realy like git too..Once i tried to make my own git server on my private
> web-server so when i finish the work i can send the customer his pdf folder
> link..but..that didnt work becouse you cant see actual files on git web
> server..like you can o
Hej thank you for all your anwsers..
I realy like git too..Once i tried to make my own git server on my private
web-server so when i finish the work i can send the customer his pdf folder
link..but..that didnt work becouse you cant see actual files on git web
server..like you can on github..
> It
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
On 04/07/2013 09:23 AM, David Kastrup wrote:
> Have you tried with LilyPond PDFs? I think they tend to compress on the
> object level which _might_ work reasonably with some of git's packing
> techniques.
No. I did take a look inside them before writing my previous email -- they
certainly have m
Janek Warchoł writes:
> 2013/4/7 David Kastrup :
>> Joseph Rushton Wakeling writes:
>>
>>> On 04/06/2013 10:50 PM, Janek Warchoł wrote:
The things is, use git for tracking source files, not pdfs. If you
put \version statements in all your .ly files, you can always recreate
a pdf
2013/4/7 David Kastrup :
> Joseph Rushton Wakeling writes:
>
>> On 04/06/2013 10:50 PM, Janek Warchoł wrote:
>>> The things is, use git for tracking source files, not pdfs. If you
>>> put \version statements in all your .ly files, you can always recreate
>>> a pdf with appropriate LilyPond versio
Joseph Rushton Wakeling writes:
> On 04/06/2013 10:50 PM, Janek Warchoł wrote:
>> The things is, use git for tracking source files, not pdfs. If you
>> put \version statements in all your .ly files, you can always recreate
>> a pdf with appropriate LilyPond version.
>>
>> Actually, it might mak
On 04/06/2013 10:50 PM, Janek Warchoł wrote:
> The things is, use git for tracking source files, not pdfs. If you
> put \version statements in all your .ly files, you can always recreate
> a pdf with appropriate LilyPond version.
>
> Actually, it might make sense to track some pdfs as well, but i
> Hi,
>
> 2013/4/6 Stjepan Horvat :
>> Hey guys .. what would you prefer using as a lilypond database. I have bunch
>> of files in bunch of folders laying around my pc with diferent versions of
>> the same song, 20 same/diffrent config files, unsorted and some of them
>> already are lost or can't f
Hi,
2013/4/6 Stjepan Horvat :
> Hey guys .. what would you prefer using as a lilypond database. I have bunch
> of files in bunch of folders laying around my pc with diferent versions of
> the same song, 20 same/diffrent config files, unsorted and some of them
> already are lost or can't find. Call
Hej guys..what would you prefer using as a lilypond database. I have bunch
of files in bunch of folder laying around my pc with diferent versions of
the same song, 20 of same/diffrent config files, unsorted and some of them
i already can't find. Call it as a local "publishing" thing.
Hey guys .. w
13 matches
Mail list logo