Re: Help with git and LilyPond Tutorial

[Johannes Schindelin]

Hi,

On Tue, 26 Dec 2006, Daniel Tonda Castillo wrote:

> SUBMIT TO GIT
> 
>    git push
> 
> If you do not have GIT write access, send patches to your translation
> sponsor, or the the lilypond-user list.

This should be expanded upon:

If you do not have GIT write access (in which case a "git push" will only 
say that permission is denied), send patches to your translation sponsor, 
or to the lilypond-user list. You can create patches like this:

1) if you branches from web/master (recommended)

        $ git format-patch web/master

   Note that you have to pull like this:

        $ git pull git://git.sv.gnu.org/lilypond.git/ web/master:web/master

   and you have to run format-patch _before_ pulling.

2) if you know how many patches you want

        $ git format-patch HEAD~5

    Replace the number "5" by the number of patches...

3) if you don't know how many patches you want, first look with

        $ git log

   for the first commit you _don't_ want. You will find a line
   "commit <cryptic-40-hex-chars>" above the commit message. Copy the 
   40 hex characters (which are the internal unique identifier for this 
   commit), and then paste them into the command line

        $ git format-patch <40-hex-chars>

All three commands will give you a number of files, all starting with 
0001-<first-line>.txt, 0002-<first-line>.txt, etc. where "<first-line>" is 
the first line of your commit messages, with spaces replaced by minuses.

> I'm sorry to pester you so much, but git seems to really be "rocket 
> science".

Once you grasped how to specify commits, it becomes easier. Please have 
a look at

        http://git.or.cz/gitwiki/QuickStart

to get a good quick start into git by examples.

Hth,
Dscho