Re: Help with git and LilyPond Tutorial

[Daniel Tonda Castillo]

Ok, here is an example for one of the files I've translated so far:

$ git add es/install/macos.html 
$ git commit -m 'add file' es/install/macos.html

Before all this happened, to get the full documentation I followed all 
instructions:

 mkdir web ; cd web
 git init-db
 touch empty ; git add empty ; git commit  -m 'empty' empty
 git pull git://git.sv.gnu.org/lilypond.git/ web/master:
 git repack.

So after finishing the first phase (all files marked as priority 1), I 
thought the safe thing to do was
commit all translations to git. But the commands in the README are not 
very helpful. It says to do: 
----------------
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.
--------------------------------

I also read the man page for git push and found out it confuses me more 
than it helps. It talks about refs/head but I have no clue what that is 
supposed to mean. I even got an account at savannah and can log in via 
the browser, but only in view mode. I tried the different incantations 
of ssh+git... commands and get this:

git push ssh+git://address@hidden/srv/git/lilypond.git/
Permission denied (publickey).
fatal: unexpected EOF

So I probably have the refs part absent.

Is there a specific sequence of commands one must do to get this working?

Since the translation to spanish doesn't exist do I have to create a 
branch (i.e. es)?

Or would it be preferable to pack the created documents in a tarball and 
send them to the devel list?

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

Daniel Tonda C.

So I thought I'd use the command as shown above, which of course I now 
know doesn't work. I looked in

Johannes Schindelin wrote:
> Hi,
>
> On Tue, 26 Dec 2006, Daniel Tonda wrote:
>
>   
> > After each modification I have done:
> >
> > git add es/<file>
> > git commit -m 'add file' es/<file>
> >     
>
> You could -- in theory -- provide a little bit more specific commit 
> messages...
>
>   
> > After finishing the translation session I've tried: git push
> >
> > I get the following output:
> >
> > $ git push
> > fatal: 'origin': unable to chdir or not a git archive
> > fatal: unexpected EOF
> >     
>
> It means that the default upstream server ("origin") is not set in your 
> setup. You should rather do something like
>
>         $ git push address@hidden:directory master:refs/heads/remote-branch
>
> where address@hidden:directory is the upstream host, and remote-branch is the 
> name you want your work to be visible after the push.
>
> I don't know what these settings are for LilyPond in your case, sorry.
>
> But once you have them, you can set the default (so that "git push" works) 
> with
>
>         $ git repo-config remote.origin.url address@hidden:directory
>         $ git repo-config remote.origin.push master:refs/heads/remote-branch
>
> Hth,
> Dscho
>
>

daniel.tonda.vcf
Description: Vcard