Graham Percival wrote Wednesday, March 25, 2009 1:06 PM
On Tue, Mar 24, 2009 at 05:15:32PM +0100, John Mandereau wrote:
Hi James,
James E. Bailey a écrit :
Leave it to me to take something easy and make it difficult. So,
I had
a conflict.
Please take half an hour to read sections "HOW CONFLIC
Graham Percival a écrit :
Ick. Do we really need to ask casual contributors to spend 30
minutes reading how to use git?
I think so, see below.
Isn't there any faster way to
give the instructions? Like
- copy the conflicted file to a backup name
- delete the file
- do "git reset --hard"
-
On Tue, Mar 24, 2009 at 05:15:32PM +0100, John Mandereau wrote:
> Hi James,
> James E. Bailey a écrit :
>> Leave it to me to take something easy and make it difficult. So, I had
>> a conflict.
> Please take half an hour to read sections "HOW CONFLICTS ARE PRESENTED"
> and "HOW TO RESOLVE CONFLI
Am 24.03.2009 um 17:15 schrieb John Mandereau:
Hi James,
James E. Bailey a écrit :
Leave it to me to take something easy and make it difficult. So, I
had a conflict. I thought I resolved it, but now tutorial.itely
looks funny. I don't know how to get back to just having the
normal files w
James, your wrote Tuesday, March 24, 2009 2:27 PM
Leave it to me to take something easy and make it difficult. So, I
had a conflict. I thought I resolved it, but now tutorial.itely
looks
funny. I don't know how to get back to just having the normal
files
without any changes that I've made, an
Hi James,
James E. Bailey a écrit :
Leave it to me to take something easy and make it difficult. So, I had
a conflict. I thought I resolved it, but now tutorial.itely looks
funny. I don't know how to get back to just having the normal files
without any changes that I've made, and I don't know i
Am 24.03.2009 um 13:42 schrieb Trevor Daniels:James E. Bailey wrote Tuesday, March 24, 2009 11:55 AM Am 24.03.2009 um 10:55 schrieb Trevor Daniels: It almost worked. I had to change @ruser{}, which addsa ref to the Notation Reference, to @ref{} which adds aref to the current manual. Yeah, see, th
On Mon, Mar 23, 2009 at 04:52:58PM +0100, Francisco Vila wrote:
> 2009/3/23 Francisco Vila :
>
> > I have git version 1.5.6.3 and both git-format-patch and
> > git[nohyphen]format-patch do work.
> >
> > James, what's the output of git --version?
>
> From your patch I see it is 1.6.2.1 ; has the h
On Mon, Mar 23, 2009 at 05:03:28PM -, Trevor Daniels wrote:
>
> James E. Bailey wrote Monday, March 23, 2009 4:45 PM
>>
>> I don't really understand how to do links in I guess this is TexInfo
>> (?) format.
>
> Yes:( Hardly the world's best mark-up language. There's
> an introduction to it i
James E. Bailey wrote Tuesday, March 24, 2009 11:55 AM
Am 24.03.2009 um 10:55 schrieb Trevor Daniels:
It almost worked. I had to change @ruser{}, which adds
a ref to the Notation Reference, to @ref{} which adds a
ref to the current manual.
Yeah, see, those are those @-commands that I don't
Am 24.03.2009 um 10:55 schrieb Trevor Daniels:
James, you wrote Monday, March 23, 2009 7:59 PM
Am 23.03.2009 um 18:03 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 4:45 PM
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009
James, you wrote Monday, March 23, 2009 7:59 PM
Am 23.03.2009 um 18:03 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 4:45 PM
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
In any event, hopefully this is an acce
Am 23.03.2009 um 18:03 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 4:45 PM
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
In any event, hopefully this is an acceptable patch. Whether or not
introduction of sing
James E. Bailey wrote Monday, March 23, 2009 4:45 PM
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
In any event, hopefully this is an acceptable patch. Whether or
not
introduction of single-staff polyphony should be kept at this
point
Am 23.03.2009 um 16:48 schrieb Trevor Daniels:
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
Am 23.03.2009 um 14:54 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 0
Am 23.03.2009 um 16:50 schrieb Francisco Vila:
2009/3/23 Carl D. Sorensen :
git format-patch is what you type at the command line.
I have git version 1.5.6.3 and both git-format-patch and
git[nohyphen]format-patch do work.
James, what's the output of git --version?
git version 1.6.2.1
_
2009/3/23 Francisco Vila :
> I have git version 1.5.6.3 and both git-format-patch and
> git[nohyphen]format-patch do work.
>
> James, what's the output of git --version?
>From your patch I see it is 1.6.2.1 ; has the hyphenated command been
deprecated? this form is still useful to invoke man page
2009/3/23 Carl D. Sorensen :
> git format-patch is what you type at the command line.
I have git version 1.5.6.3 and both git-format-patch and
git[nohyphen]format-patch do work.
James, what's the output of git --version?
--
Francisco Vila. Badajoz (Spain)
The incredible carnival of Badajoz
htt
James E. Bailey wrote Monday, March 23, 2009 2:15 PM
Am 23.03.2009 um 14:54 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey
wrote:
Yes, I d
On 3/23/09 8:19 AM, "Trevor Daniels" wrote:
>
>
> James E. Bailey wrote March 23, 2009 12:43 PM
>>
>> Am 23.03.2009 um 13:24 schrieb Trevor Daniels:
>>
>> I'd like to say that I think removing polyphony here is a viable
>> solution, but I don't really believe that. Vocal music is heavily
>
Am 23.03.2009 um 15:54 schrieb Graham Percival:
In any event, hopefully this is an acceptable patch. Whether or not
introduction of single-staff polyphony should be kept at this
point in
the LM (since doing so does not follow Documentation policy) is a
different conversation.
The patch look
On Mon, Mar 23, 2009 at 03:15:51PM +0100, James E. Bailey wrote:
>
> Am 23.03.2009 um 14:54 schrieb Graham Percival:
>
>> Good point. There should be a file called
>> 0001-something
>> in the top of the git directory. That's what you send. I'll add
>> this to the CG.
>
> Is it just me, or did th
t;James E. Bailey"
To: "Trevor Daniels"
Cc: "Carl D. Sorensen" ; "lilypond-devel"
; "lilypond-user Mailinglist" u...@gnu.org>
Sent: Monday, March 23, 2009 11:51 AM
Subject: Re: an LM update
Am 17.03.2009 um 10:39 schrieb Trevor Daniels:
Hi James
Am 23.03.2009 um 14:54 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
Yes, I did git commit -a and had the line : Modified:
Documen
On Mon, Mar 23, 2009 at 02:50:45PM +0100, James E. Bailey wrote:
>
> Am 23.03.2009 um 14:14 schrieb Graham Percival:
>
>> On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
>>>
>>> Yes, I did git commit -a and had the line : Modified: Documentation/
>>> user/tutorial.itely in that fil
Am 23.03.2009 um 14:14 schrieb Graham Percival:
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
Yes, I did git commit -a and had the line : Modified: Documentation/
user/tutorial.itely in that file. The problem is that I don't have
git-format-patch. bash reports command not f
Am 23.03.2009 um 14:14 schrieb Graham Percival:
After a few more painful iterations, the CG will contain exactly
the commands you need, so you won't *need* to know anything about
git. If you want to learn more, there's CG 1.4, but I personally
haven't read it and don't plan to do so. Ever[1].
On 3/23/09 6:25 AM, "James E. Bailey" wrote:
>>
>> Are you using Git? then use git-format-patch to generate the patch;
>> otherwise, use diff -u to obtain a diff with context lines.
>>
>> --
>> Francisco Vila. Badajoz (Spain)
>>
>> The incredible carnival of Badajoz
>> http://www.flickr.com/
James E. Bailey a écrit :
Incidentally, although the instructions in the Contributor's Guide are
generally simple enough for even me to follow, apparently they're
missing something because the git-format-patch HEAD doesn't work.
If you have a recent Git, it should probably be
git format-patch
James E. Bailey wrote:
Am 23.03.2009 um 13:50 schrieb Francisco Vila:
2009/3/23 James E. Bailey :
Incidentally, although the instructions in the Contributor's Guide are
generally simple enough for even me to follow, apparently they're
missing
something because the git-format-patch HEAD does
On Mon, Mar 23, 2009 at 02:03:56PM +0100, James E. Bailey wrote:
>
> Yes, I did git commit -a and had the line : Modified: Documentation/
> user/tutorial.itely in that file. The problem is that I don't have
> git-format-patch. bash reports command not found.
Sorry, you're (quite sensibly) looki
Am 23.03.2009 um 13:50 schrieb Francisco Vila:
2009/3/23 James E. Bailey :
Incidentally, although the instructions in the Contributor's Guide
are
generally simple enough for even me to follow, apparently they're
missing
something because the git-format-patch HEAD doesn't work.
It is HEA
2009/3/23 James E. Bailey :
> Incidentally, although the instructions in the Contributor's Guide are
> generally simple enough for even me to follow, apparently they're missing
> something because the git-format-patch HEAD doesn't work.
It is HEAD^ after your commit
--
Francisco Vila. Badajoz (
he list
Trevor
- Original Message - From: "Trevor Daniels"
To: "James E. Bailey"
Sent: Monday, March 23, 2009 12:24 PM
Subject: Re: an LM update
Hi James
Thanks for doing this, but it doesn't seem to apply. I'm not
familiar enough with patches to i
ction in the LM, with pointers to the more
thorough version in the NR is the best solution.
Trevor
- Original Message - From: "James E. Bailey"
To: "Trevor Daniels"
Cc: "Carl D. Sorensen" ; "lilypond-devel"
; "lilypond-user Mailing
Sorry - forgot to cc the list
Trevor
- Original Message -
From: "Trevor Daniels"
To: "James E. Bailey"
Sent: Monday, March 23, 2009 12:24 PM
Subject: Re: an LM update
Hi James
Thanks for doing this, but it doesn't seem to apply. I'm not
familiar e
Am 23.03.2009 um 13:06 schrieb Francisco Vila:
2009/3/23 James E. Bailey :
Attached is my attempt to make a .diff. It's my first time, so if
I didn't
do it right, let me know. It's a learning process for me.
Are you using Git? then use git-format-patch to generate the patch;
otherwise, use
2009/3/23 James E. Bailey :
> Attached is my attempt to make a .diff. It's my first time, so if I didn't
> do it right, let me know. It's a learning process for me.
Are you using Git? then use git-format-patch to generate the patch;
otherwise, use diff -u to obtain a diff with context lines.
--
Am 17.03.2009 um 10:39 schrieb Trevor Daniels:
Hi James
You wrote Tuesday, March 17, 2009 9:00 AM
On 17.03.2009, at 00:47, Carl D. Sorensen wrote:
On 3/16/09 11:52 AM, "James E. Bailey"
wrote:
On 16.03.2009, at 16:43, Graham Percival wrote:
c) Can we just make the change so th
Hi James
You wrote Tuesday, March 17, 2009 9:00 AM
On 17.03.2009, at 00:47, Carl D. Sorensen wrote:
On 3/16/09 11:52 AM, "James E. Bailey"
wrote:
On 16.03.2009, at 16:43, Graham Percival wrote:
c) Can we just make the change so that more people aren't
confused by
the issue. (I'v
On 17.03.2009, at 00:47, Carl D. Sorensen wrote:
On 3/16/09 11:52 AM, "James E. Bailey"
wrote:
On 16.03.2009, at 16:43, Graham Percival wrote:
c) Can we just make the change so that more people aren't
confused by
the issue. (I've answered another question related to this in the
On 3/16/09 11:52 AM, "James E. Bailey" wrote:
>
>
> On 16.03.2009, at 16:43, Graham Percival wrote:
>>
>>> c) Can we just make the change so that more people aren't confused by
>>> the issue. (I've answered another question related to this in the
>>> last
>>> week)
>>
>> Yes, please do. C
On 16.03.2009, at 16:43, Graham Percival wrote:
c) Can we just make the change so that more people aren't confused by
the issue. (I've answered another question related to this in the
last
week)
Yes, please do. Carl can help you get started as a Frog; we
desperately need more people writ
On Fri, Mar 06, 2009 at 09:31:54AM +0100, James E. Bailey wrote:
> I realise it's only been a week since this was last discussed, but:
> a) no one who can say whether or not this can be implemented has
> responded (ever)
Yes, this can be implemented.
I have no clue how complicated this may be,
2009/3/6 James E. Bailey :
> The dontDie is necessary to keep the voices alive.
Well done; added as http://code.google.com/p/lilypond/issues/detail?id=761
Regards,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/m
El 06.03.2009, a las 11:36, Valentin Villenave escribió:
2009/3/6 James E. Bailey :
Another feature request - \set Voice.keepAlive = ##t ?
That would be awesome.
I'll add it as soon as you give me a minimal example as well :)
Regards,
Valentin
From my previous example:
\version "2.12.2"
2009/3/6 James E. Bailey :
>> Another feature request - \set Voice.keepAlive = ##t ?
>
> That would be awesome.
I'll add it as soon as you give me a minimal example as well :)
Regards,
Valentin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
ht
ikely to be implemented. So, what's the chance
this change will be made? I've no idea whether it is easy or
difficult.
Trevor
- Original Message - From: "James E. Bailey"
To: "lilypond-user Mailinglist" ;
"lilypond- devel"
Sent: Friday,
ll be made? I've no idea whether it is easy or
difficult.
Trevor
- Original Message - From: "James E. Bailey"
To: "lilypond-user Mailinglist" ;
"lilypond- devel"
Sent: Friday, February 27, 2009 9:54 PM
Subject: Fwd: an LM update
Since I haven'
whether it is easy or
difficult.
Trevor
- Original Message - From: "James E. Bailey"
To: "lilypond-user Mailinglist" ; "lilypond-
devel"
Sent: Friday, February 27, 2009 9:54 PM
Subject: Fwd: an LM update
Since I haven't heard any feedback, I th
rom: "James E. Bailey"
To: "lilypond-user Mailinglist" ;
"lilypond-devel"
Sent: Friday, February 27, 2009 9:54 PM
Subject: Fwd: an LM update
Since I haven't heard any feedback, I thought I would post to
the - devel list as well. Incidentally, I've answer
Since I haven't heard any feedback, I thought I would post to the -
devel list as well. Incidentally, I've answered questions directly
related to this twice in the last week or so.
Since the NR has the wonderful introduction to single-staff
polyphony, can this be simply inserted into the L
52 matches
Mail list logo
