Jan,
can you add a list of exceptions to your copyright year update script?
Some files like the mf2pt1 stuff are contributed and should stay
as-is. I've fixed that manually in the git, but an automatic process
would be better.
Werner
___
lilypo
On 1/6/09 9:32 PM, "Valentin Villenave" wrote:
> 2009/1/6 Carl D. Sorensen :
>
>> Then you create a symbolic link in the main binary lilypond directory to the
>> ly/, scm/ and input/ directories from your git repository. Now, although
>> the directories are actually in your git repository, t
2009/1/6 Carl D. Sorensen :
> Then you create a symbolic link in the main binary lilypond directory to the
> ly/, scm/ and input/ directories from your git repository. Now, although
> the directories are actually in your git repository, they appear to the
> binary to be in the binary directory.
On 1/6/09 6:57 PM, "Andrew Hawryluk" wrote:
> Carl, when you are working on something, do you commit your changes to
> your local repository every day? Would my final patch become a single
> commit even if I made the changes in several small commits locally?
> (I'm trying to avoid commit clutt
Seems pretty clear to me. Thanks.
andrew
2009/1/6 Carl D. Sorensen
> First of all, I think that the easiest way to develop LilyPond is to have a
> buildable source tree, and I'd recommend it for anybody who's willing to go
> to the effort to get it.
>
> But with a little bit of directory magic
On 1/5/09 5:16 PM, "Andrew Wilson" wrote:
> HI Carl,
>
> You keep saying that we don't need to build because
> the lily files and the scheme files are interpreted and
> are loaded at runtime. If we're working in a copy of
> the GIT repository then it won't have a binary to run.
> If we work
HI Carl,
You keep saying that we don't need to build because
the lily files and the scheme files are interpreted and
are loaded at runtime. If we're working in a copy of
the GIT repository then it won't have a binary to run.
If we work in a downloaded binary distribution then
the changes aren't g
Ian,
On 1/5/09 3:40 PM, "Ian Hulin" wrote:
> Hi Carl,
> \oladdlyrics is on my to-do list of undocumented functions.
> \oldaddlyrics is the deprecated version of \addlyrics.
> Should I remove the oldaddlyrics entry and add in one for \addlyrics so
> this one is included in the docs, or just put
I'm installing it now. If this works it will be fabulous and I'll be
removing
the cygwin installation. I'm going out in about 20 mins, hopefully it will
be installed when I get back. I'll let you know how it get on.
andrew
2009/1/5 Carl D. Sorensen
>
>
>
> On 1/5/09 10:19 AM, "Valentin Ville
On 1/5/09 10:19 AM, "Valentin Villenave" wrote:
> 2009/1/5 Carl D. Sorensen :
>
>> I'd recommend establishing a dual boot system with a Linux partition that
>> you use for building LilyPond. It was lots easier for me.
>
> The easiest solution for a Windows user being without a doubt
> http:
2009/1/5 Carl D. Sorensen :
> I'd recommend establishing a dual boot system with a Linux partition that
> you use for building LilyPond. It was lots easier for me.
The easiest solution for a Windows user being without a doubt
http://wubi-installer.org/
(no partitioning needed)
Cheers,
Valentin
Carl, when you are working on something, do you commit your changes to
your local repository every day? Would my final patch become a single
commit even if I made the changes in several small commits locally?
(I'm trying to avoid commit clutter on the Savannah repo.)
How often do you re-sync with
2009/1/6 Patrick McCarty :
> I can't do a `make all' on the current git master, and this patch
> fixes the problem. Can someone apply it?
Thanks, applied.
Cheers,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/ma
Hello,
I can't do a `make all' on the current git master, and this patch
fixes the problem. Can someone apply it?
Thanks,
Patrick
From ab347e3e065dc69c4630be331d52aaa1db905ec0 Mon Sep 17 00:00:00 2001
From: Patrick McCarty
Date: Tue, 6 Jan 2009 14:20:51 -0800
Subject: [PATCH] Fix compile
Signe
2009/1/6 Trevor Daniels :
>> It's a dos limitation that has carried into Windows. And it bites
>> professionals. I recently had to teach my fellow (experienced!) programmers
>> that certain file names weren't permitted...
I recently had to run Windows Vista (for the only good reason one can
think
Hi,
adding to this old thread:
Was there already discussion on translating also the NEWS part of the
documentation? It might not be really used by many people when 2.12 has
become normality but for the moment it might be interesting since it
also has a direct link from the news entry on lilyp
Reinhold, you wrote Tuesday, January 06, 2009 7:02 PM
Am Sonntag, 4. Januar 2009 13:16:02 schrieb Trevor Daniels:
Clicking on (for example) Snippets: Section "Pitches" in Snippets
on page 2 of the NR takes you to the pitches snippet list, but
then clicking on the link back to Pitches at the to
On Tue, Jan 6, 2009, Trevor Daniels said:
> The names are case-insensitive, and they cannot be
> used as directory names or the first part of a
> filename (the bit before the dot).
please note, in DOS (and many of its contemporary file systems), what
users think of as the filename is not actua
Anthony W. Youngman wrote Tuesday, January 06, 2009 7:09 PM
In message , Trevor
Daniels writes
Aargh. This commit also implies creation of scripts/aux/. I don't
enjoy so much saying this, but the limitation we hit is worthwhile:
Windows sucks, I wish there were only Unix OSes. :-)
I can't
In message , Trevor
Daniels writes
Aargh. This commit also implies creation of scripts/aux/. I don't
enjoy so much saying this, but the limitation we hit is worthwhile:
Windows sucks, I wish there were only Unix OSes. :-)
I can't really apologise for Windows, and I wasn't aware of this
limit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 4. Januar 2009 13:16:02 schrieb Trevor Daniels:
> Clicking on (for example) Snippets: Section "Pitches" in Snippets
> on page 2 of the NR takes you to the pitches snippet list, but
> then clicking on the link back to Pitches at the top of t
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the German team of translators. The file is available at:
http://translationproject.org/latest/lilypond/de.po
(We can arrange things so that
John Mandereau Tuesday, January 06, 2009 12:06 AM
Le lundi 05 janvier 2009 à 15:32 +, Trevor Daniels a écrit :
I have a git problem with your recent commit
c553fc2251b508befebd1dc297c4baa898463f34 to clean up the build scripts.
The reason is that aux is a reserved word in Windows, alon
Trevor Daniels wrote:
> Look up layers in the Notation Reference index. The
> relevant sentence there is "The order of printing objects
> with the same value of 'layer is indeterminate."
>
> Setting 'layer explicitly may solve your problem.
Trevor,
Amazing. Now it works. Mystery solved.
Thanks
24 matches
Mail list logo
