On Wed, Jan 1, 2014 at 5:16 PM, Urs Liska wrote:
> Am 01.01.2014 18:34, schrieb Phil Holmes:
>
>> - Original Message - From: "Urs Liska"
>> To: "LilyPond Development Team"
>> Sent: Wednesday, January 01, 2014 5:03 PM
>> Subject: Content of "Introduction"->"Our Goal"
>>
>> [snip]
>>
>> I
Good, except we want to keep the information that Git works usefully on
Windows.
https://codereview.appspot.com/46120044/diff/1/Documentation/contributor/source-code.itexi
File Documentation/contributor/source-code.itexi (left):
https://codereview.appspot.com/46120044/diff/1/Documentation/contr
Am 01.01.2014 18:34, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
To: "LilyPond Development Team"
Sent: Wednesday, January 01, 2014 5:03 PM
Subject: Content of "Introduction"->"Our Goal"
[snip]
I think the sentence could be:
"The result is a system which frees composer
Benkő Pál writes:
> 2014/1/1 :
>>
>> Janek, when people start with `git clone` do they also get a staging
>> branch that tracks the one on savannah?
>> I think we still want at least one mention of how to set up a 'staging'
>> branch to track origin/staging,
>> git checkout --track -b staging
2014/1/1 :
>
> Janek, when people start with `git clone` do they also get a staging
> branch that tracks the one on savannah?
> I think we still want at least one mention of how to set up a 'staging'
> branch to track origin/staging,
> git checkout --track -b staging origin/staging
you can set
https://codereview.appspot.com/46120044/diff/1/Documentation/contributor/source-code.itexi
File Documentation/contributor/source-code.itexi (left):
https://codereview.appspot.com/46120044/diff/1/Documentation/contributor/source-code.itexi#oldcode729
Documentation/contributor/source-code.itexi:72
On 01/01/14 17:50, Jean-Charles Malahieude wrote:
Le 01/01/2014 18:07, Urs Liska disait :
Am 01.01.2014 18:02, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
But you're led to believe that LilyDev is the canonical environment
for working on LilyPond, and if you dare to g
- Original Message -
From: "Jean-Charles Malahieude"
To: "Urs Liska" ; "Phil Holmes" ;
Sent: Wednesday, January 01, 2014 5:50 PM
Subject: Re: contributing instructions are misleading!
Le 01/01/2014 18:07, Urs Liska disait :
Am 01.01.2014 18:02, schrieb Phil Holmes:
- Original
Le 01/01/2014 18:07, Urs Liska disait :
Am 01.01.2014 18:02, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
But you're led to believe that LilyDev is the canonical environment
for working on LilyPond, and if you dare to go another route you'll be
on your own and heading f
- Original Message -
From: "Urs Liska"
To: "LilyPond Development Team"
Sent: Wednesday, January 01, 2014 5:03 PM
Subject: Content of "Introduction"->"Our Goal"
[snip]
I think the sentence could be:
"The result is a system which frees composers from the details of layout,
allowing th
- Original Message -
From: "Urs Liska"
To: "Phil Holmes" ;
Sent: Wednesday, January 01, 2014 5:07 PM
Subject: Re: contributing instructions are misleading!
Well - since you're the only one running your specific environment,
that's generally true. With a VM that many of us run, it's n
Urs Liska writes:
> Am 01.01.2014 18:02, schrieb Phil Holmes:
>> - Original Message - From: "Urs Liska"
>>
>>> But you're led to believe that LilyDev is the canonical environment
>>> for working on LilyPond, and if you dare to go another route you'll be
>>> on your own and heading for tr
Am 01.01.2014 18:02, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
To:
Sent: Wednesday, January 01, 2014 4:41 PM
Subject: Re: contributing instructions are misleading!
That's a point I'd like to say something about.
The CG's insistence on Lilydev can be somewhat offputt
I see the need to modify the "Our Goal" box on "Introduction", but I
wouldn't want to do that on my own because it would feel like modifying
someone else's tune instead of only adding a figured bass to it.
So I'd like to get some feedback here and propose a patch only then.
Here are my thought
- Original Message -
From: "Urs Liska"
To:
Sent: Wednesday, January 01, 2014 4:41 PM
Subject: Re: contributing instructions are misleading!
That's a point I'd like to say something about.
The CG's insistence on Lilydev can be somewhat offputting. I didn't think
I'd need Lilydev and
Am 01.01.2014 15:47, schrieb Janek Warchoł:
2014/1/1 Graham Percival :
On Tue, Dec 31, 2013 at 06:35:36PM +0100, Janek Warchoł wrote:
2013/12/12 Graham Percival :
Sorry, this awoke Grumpy Graham.
I should have expected that.
Yes, you should have. :P Happy new year, BTW.
And you too!
James writes:
> There are some quirks (for me) that might be easier to explain or
> resolve as a 'non git-fu-er' such as:
>
> It seems that the 'update source' button doesn't update staging, only
> master, so I always have to run git checkout staging, git pull and
> then merge staging manually wi
On 07/12/13 18:33, Carl Sorensen wrote:
On 11/29/13 12:52 PM, "James" wrote:
1. Git checkout [branch] on the command line. That's fine I can handle
that :)
Where [branch] is going to be Staging 99% of the time (but for the case
where I whined, it was stable/2.18)
2. Then run lily-git.tcl fr
Janek Warchoł writes:
> Ah, you're absolutely right!
> My point is The Golden Rule: he who does the work, makes the rules ;-)
If you define "does the work" as "makes any change" which includes
_undoing_ previous work, then this can be more succinctly expressed as
"there are no rules".
--
David
On 30/12/13 22:06, Martin Tarenskeen wrote:
On Mon, 30 Dec 2013, Martin Tarenskeen wrote:
" view ps with ghostview
map :!gv --watch "%<.pdf" &
the comment should be fixed also :-) :
" view pdf with ghostview
(Personally I would choose another PDF viewer, but that's another story.
2014/1/1 Graham Percival :
> On Tue, Dec 31, 2013 at 06:35:36PM +0100, Janek Warchoł wrote:
>> 2013/12/12 Graham Percival :
>> > Sorry, this awoke Grumpy Graham.
>>
>> I should have expected that.
>
> Yes, you should have. :P Happy new year, BTW.
And you too!
>> Anyway, there are two parts to
Fine, apart from throwing away the Windows
section.
https://codereview.appspot.com/46120044/diff/1/Documentation/contributor/source-code.itexi
File Documentation/contributor/source-code.itexi (left):
https://codereview.appspot.com/46120044/diff/1/Documentation/contributor/source-code.itexi#oldc
22 matches
Mail list logo
