Mark Polesky wrote Wednesday, January 06, 2010 4:18 AM
Trevor Daniels wrote:
The section headings need to make it clearer what audience
is being addressed. Perhaps
Summary for experienced Unix developers
Full details for new contributors
Then of course there is a lot more to add to provide
Hello all,
I have done some work to issue 659. I have drwan the alternate segno
symbol and
in addition, I'll provide new bar commands for easier use.
But I don't manage to upload it to rietveld.
1) I have a google account
2) I have downloaded git-cl
3) I have a branch called "varsegno" in my
Han-Wen Nienhuys schrieb:
On Tue, Jan 5, 2010 at 5:36 PM, Marc Hohl wrote:
Han-Wen Nienhuys schrieb:
I am confused here. Are you trying to implement the symbols that are
on the tab staff, or on the normal notation?
Both. But first, I want to concentrate on the pointed slurs i
On 01/05/2010 04:10 PM, Jan Nieuwenhuizen wrote:
> Op dinsdag 05-01-2010 om 16:00 uur [tijdzone +0200], schreef Dave
> Plater:
>
>> On 01/05/2010 03:16 PM, Jan Nieuwenhuizen wrote:
>>
>>> Op dinsdag 05-01-2010 om 11:38 uur [tijdzone +0200], schreef Dave
>>> Plater:
>>>
>
>> "/usr/
Trevor Daniels wrote:
>>> Summary for experienced Unix developers
>>> Full details for new contributors
>>>
>>> Then of course there is a lot more to add to provide
>>> "full details". But that can come later.
>>
>> Well, this is just the introduction. Full details will
>> come in the chapter on
Am Mittwoch, 6. Januar 2010 09:45:20 schrieb Marc Hohl:
> the files, then
>
> $ git commit,
>
> then
>
> $ git format-patch origin
That's not needed for git-cl
> and afterwards
>
> $git cl upload
>
> which I obtained from gitk &
Ah, so there's the misconception:
git-cl does NOT upload the
Reinhold Kainhofer schrieb:
Am Mittwoch, 6. Januar 2010 09:45:20 schrieb Marc Hohl:
the files, then
$ git commit,
then
$ git format-patch origin
That's not needed for git-cl
and afterwards
$git cl upload
which I obtained from gitk &
Ah, so there's the misconception:
g
Hello all,
I've just posted a patch for the alternate segno sign.
To use the new symbol stored at scripts.varsegno, I have
adapted the arguments for the \bar command.
To start a sengo part, you can use
\bar ".§" or \bar "§"
at the end of the segno part, use \bar "§.".
The difference between ".§"
On 1/6/10 1:45 AM, "Marc Hohl" wrote:
> Hello all,
>
> I have done some work to issue 659. I have drwan the alternate segno
> symbol and
> in addition, I'll provide new bar commands for easier use.
>
> But I don't manage to upload it to rietveld.
>
> 1) I have a google account
> 2) I have d
Carl Sorensen schrieb:
[...]
You can test this out before using git-cl by doing
git diff
and seeing what is reported.
This is very helpful - thanks!
Marc
HTH,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gn
I haven't tried this out, but some things simply jump out..
http://codereview.appspot.com/181144/diff/1/3
File lily/bar-line.cc (right):
http://codereview.appspot.com/181144/diff/1/3#newcode96
lily/bar-line.cc:96: Stencil segno = Font_interface::get_default_font
(me)->find_by_name ("scripts.var
reinhold.kainho...@gmail.com schrieb:
I haven't tried this out, but some things simply jump out..
http://codereview.appspot.com/181144/diff/1/3
File lily/bar-line.cc (right):
http://codereview.appspot.com/181144/diff/1/3#newcode96
lily/bar-line.cc:96: Stencil segno = Font_interface::get_defaul
Hi, I maintain lilypond on openSUSE and am having a problem compiling
the documentation, a local build with rpmbuild succeeds but a chrooted
build fails seemingly on a ghostscript command. I've come to the
conclusion, after many long builds (one and a half hours locally and
half hour online), that
On 01/07/2010 08:31 AM, Dave Plater wrote:
> Hi, I maintain lilypond on openSUSE and am having a problem compiling
> the documentation, a local build with rpmbuild succeeds but a chrooted
> build fails seemingly on a ghostscript command. I've come to the
> conclusion, after many long builds (one an
14 matches
Mail list logo
