Hello guys,
Graham Percival percival-music.ca> wrotes
> > > Yes, I'm a very "nice" person. ;)
> >
> > The humor like yours may be called "Oyaji Gyagu" in Japan
>
> Hidoi! Boku wa oyaji desu? Boku wa tada san-juu-sai! :(
>
> Translation: you're mean! I'm an old man? I'm only 30 years old
Carl D. Sorensen wrote:
Applied like a charm -- no warnings, everything was smooth as silk.
Yea! It worked! Not sure what could be up on Trevor's end...
Pushed to origin.
Carl
Thanks Carl. I think I have my doc-patch workflow now and it should be
easier for y'all as a consequence. Ma
Applied like a charm -- no warnings, everything was smooth as silk.
Pushed to origin.
Carl
On 2/20/09 5:13 PM, "Jonathan Kulp" wrote:
> Here's a patch for the CG git section created using git. My repo is a fresh
> checkout and the file on my machine has unix line endings and whitespaces
> st
Here's a patch for the CG git section created using git. My repo is a fresh
checkout and the file on my machine has unix line endings and whitespaces
stripped. I hope it works o.k. Trevor has had trouble with the last couple
of patches I've sent. Carl, could you try applying this one, too? Tha
Trevor Daniels wrote:
Jonathan Kulp wrote Friday, February 20, 2009 2:58 PM
You have removed all the whitespace, but the lines still
have Windows line terminations (CR-LF). I fixed that, but
I'm afraid it still doesn't apply. I honestly don't
know whether the problem is at my end or yours. M
Jonathan Kulp wrote Friday, February 20, 2009 2:58 PM
Graham Percival wrote:
On Fri, Feb 20, 2009 at 08:09:21AM -0600, Jonathan Kulp wrote:
Is this right? I surmise that this pulls down more code than
strictly
necessary for working on docs, but I don't mind having the extra
code.
Maybe I
I forward this to -devel, if there is no inconvenient and nobody does
it before, I could apply it next Tue or Wed.
-- Forwarded message --
From: Francisco Vila
Date: 2009/2/19
Subject: Re: Strange output from convert-ly
To: Mats Bengtsson
Cc: Robin Bannister , lilypond-user
20
Could you add the command to appendix B.8.3 of the manual? And maybe
change the example for the \postscript command. Otherwise, lgtm
http://codereview.appspot.com/12660
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailma
On Fri, Feb 20, 2009 at 01:05:24PM +0100, Jan Nieuwenhuizen wrote:
> On do, 2009-02-19 at 13:41 -0800, Patrick McCarty wrote:
>
> > Bumping gmp to 4.2.4 for darwin-x86, and removing the patch and
> > configure_command (), fixed the darwin-x86 build for me.
>
> Ok, great. Do you have a patch? Ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 1. Februar 2009 schrieb Graham Percival:
> Unless anybody complains within the next 48 hours, we'll switch to
> 2.13 and get started with all the major changes. If somebody
> complains, then we'll wait until 2.12.3 is out, and then move to
Johannes Schindelin wrote:
--track ?
That probably means that you have an older Git than I have (I am always on
the bleeding edge). In that case, you might need to use
$ git checkout --track -b web origin/web
(Newer Git assumes that "checkout -t origin/web" is a shortcut for this
Hi,
On Fri, 20 Feb 2009, Jonathan Kulp wrote:
> Johannes Schindelin wrote:
>
> > No need to reclone. Just rename the current branch:
> >
> > $ git branch -m old.branch
> >
>
> This part seemed to work fine.
>
> > And then start anew (in the same repository!):
> >
> > $ git checkout -t or
Graham Percival wrote:
On Fri, Feb 20, 2009 at 08:09:21AM -0600, Jonathan Kulp wrote:
Is this right? I surmise that this pulls down more code than strictly
necessary for working on docs, but I don't mind having the extra code.
Maybe I should delete the whole directory and do a fresh clone.
I'm going away for carnival, but reviewed 2 patches for you.
On Fri, Feb 20, 2009 at 7:36 AM, Reinhold Kainhofer
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Apparently, my message got lost somewhere in the mail flood of lily-devel, so
> I'm reposting my request for review of se
Johannes Schindelin wrote:
No need to reclone. Just rename the current branch:
$ git branch -m old.branch
This part seemed to work fine.
And then start anew (in the same repository!):
$ git checkout -t origin/web
(You need to adjust the "web" to the appropriate branch na
On Fri, Feb 20, 2009 at 08:09:21AM -0600, Jonathan Kulp wrote:
> Is this right? I surmise that this pulls down more code than strictly
> necessary for working on docs, but I don't mind having the extra code.
> Maybe I should delete the whole directory and do a fresh clone.
Oh, I forgot to men
On Fri, Feb 20, 2009 at 08:09:21AM -0600, Jonathan Kulp wrote:
> Is this right? I surmise that this pulls down more code than strictly
> necessary for working on docs, but I don't mind having the extra code.
> Maybe I should delete the whole directory and do a fresh clone.
Don't do a clone; j
Hi,
On Fri, 20 Feb 2009, Jonathan Kulp wrote:
> Trevor Daniels wrote:
>
> > More seriously, the patch doesn't apply here because
> > your line numbering seems to be 1 off from the line
> > numbers I have in git-starting.itexi. I have no idea
> > why that should be. I believe my git repo is ful
Trevor Daniels wrote:
More seriously, the patch doesn't apply here because
your line numbering seems to be 1 off from the line
numbers I have in git-starting.itexi. I have no idea
why that should be. I believe my git repo is fully
synch'ed with origin/master, and according to your
description
Jonathan, you wrote Thursday, February 19, 2009 12:16 PM
Trevor Daniels wrote:
Jon, the recent patch I pushed for you (lsr-work.patch) was
sent using Thunderbird but, as it was attached, the line
endings were correctly Unix (LF only). It did have white
space at the end of most (every, maybe)
On do, 2009-02-19 at 13:41 -0800, Patrick McCarty wrote:
Hi Patrick,
> Bumping gmp to 4.2.4 for darwin-x86, and removing the patch and
> configure_command (), fixed the darwin-x86 build for me.
Ok, great. Do you have a patch? Han-Wen, can you verify and apply?
Jan.
--
Jan Nieuwenhuizen | G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Apparently, my message got lost somewhere in the mail flood of lily-devel, so
I'm reposting my request for review of several patches:
Any objections to applying these patches (those with a convert-ly rule of
course only after 2.13 has been opened)?
h
22 matches
Mail list logo
