explain how to add git-cl to PATH

explain how to add git-cl to PATH

i know modifying PATH is basic knowledge,
but i'm windows man and figuring this out
took me 15 minutes... too long.

[Carl, 2012-01-03 21:55:09]

I hesitate to do this because is it OS-specific.

I think if we are going to do it, we should clearly mark this line as applying
to lilydev and similar systems.

When we do this, we are diving development towards only occuring on lilydev. 
Maybe that's OK, but it seems unnecessary to me.

Thanks,

Carl

http://codereview.appspot.com/5503093/diff/1/Documentation/contributor/source...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5503093/diff/1/Documentation/contributor/source...
Documentation/contributor/source-code.itexi:917:
@command{PATH=~/type-here-directory-containing-git-cl:"${PATH}"}
If we are going to do this, we should probably have the line be in an @example

[Graham Percival, 2012-01-03 22:05:58]

Most linux distributions use bash, so this isn't a terrible idea.  But you need
to log out and log back in for the change to take effect.

http://codereview.appspot.com/5503093/diff/1/Documentation/contributor/source...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5503093/diff/1/Documentation/contributor/source...
Documentation/contributor/source-code.itexi:917:
@command{PATH=~/type-here-directory-containing-git-cl:"${PATH}"}
On 2012/01/03 21:55:09, Carl wrote:
> If we are going to do this, we should probably have the line be in an @example

+1

[janek, 2012-01-05 01:08:01]

second draft

http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
Documentation/contributor/source-code.itexi:921: @example
should all this be in a Note?

[pkx166h, 2012-01-05 06:05:23]

http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
Documentation/contributor/source-code.itexi:921: @example
On 2012/01/05 01:08:01, janek wrote:
> should all this be in a Note?

I think you could make this much simpler.

See the section

http://lilypond.org/doc/v2.15/Documentation/contributor-big-page#problems

Compiling on Mac OS X

Follow that style. Were this me making this edit, I'd lift this section and just
reword the bits for LilyDev.

There is some assumption that if you've managed to install and get this far with
LilyDev that you can handle cut-down instructions.

Otherwise generally:

use @example for just the stuff you'd type in the terminal, not any additional
instructions. This makes it much clearer especially on the web pages.

[janek, 2012-01-06 10:15:47]

third draft.

http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
Documentation/contributor/source-code.itexi:921: @example
On 2012/01/05 06:05:23, J_lowe wrote:
> Were this me making this edit, I'd lift this section

"lift this section" = ?

> and just reword the bits for LilyDev.

[pkx166h, 2012-01-06 11:07:29]

On 2012/01/06 10:15:47, janek wrote:
> third draft.
> 
>
http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
> File Documentation/contributor/source-code.itexi (right):
> 
>
http://codereview.appspot.com/5503093/diff/4001/Documentation/contributor/sou...
> Documentation/contributor/source-code.itexi:921: @example
> On 2012/01/05 06:05:23, J_lowe wrote:
> > Were this me making this edit, I'd lift this section
> 
> "lift this section" = ?

Sorry, an English Idiom. "lift this section" = "Copy and Paste this section"

[janek, 2012-01-06 11:45:03]

On 2012/01/06 11:07:29, J_lowe wrote: 
> Sorry, an English Idiom.
> "lift this section" = "Copy and Paste this section"

No problem.  So it's ok now?

PS sorry for previous mail, i had to check something about git-cl

[Graham Percival, 2012-01-09 05:02:56]

LGTM

[janek, 2012-01-11 04:42:47]

pushed to staging and closed.

[Graham Percival, 2012-01-11 05:44:16]

this fails to compile.  Removed from staging.

[dak, 2012-01-11 07:32:45]

http://codereview.appspot.com/5503093/diff/4003/Documentation/contributor/sou...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5503093/diff/4003/Documentation/contributor/sou...
Documentation/contributor/source-code.itexi:926:
PATH=~/type-here-directory-containing-git-cl:"${PATH}"
$@{PATH@}

[janek, 2012-01-15 23:00:49]

Necessary @'s were added, patch was pushed as
67f64c0bdf4cd469de73b135df5ba61cbfea15f7