Re: master branch ambiguous

2006-11-11 Thread Werner LEMBERG
> You have to use > >git push ssh:-savannah-addres- mybranch:refs/heads/master > > to push to the main master branch. Have I? My fingers have just been faster than my brain, and I just typed `git-push', without any arguments, and everything seems to be fine, according to http://git.sv.

Re: \concat markup command

2006-11-11 Thread Werner LEMBERG
> > I thus suggest a command \concat which does the same as \line but > > without inserting whitespace: > > Isn't this more efficiently done by setting word-space to 0.0 and > interpreting as a line? Isn't this what my command does? What do you mean with `efficiently'? Werner ___

master branch ambiguous

2006-11-11 Thread Han-Wen Nienhuys
hi, i've just finished setting up the git repository on savannah, and I've hit the first snag. There are two master branches (one for lilypond, and web/master for the website). This makes pushing a bit awkward. You have to use git push ssh:-savannah-addres- mybranch:refs/heads/master to

Re: \concat markup command

2006-11-11 Thread Han-Wen Nienhuys
Werner LEMBERG escreveu: All markup commands which accept more than a single markup put spaces inbetween. However, sometimes this is not useful (for example, just look at the bad appearance of the E=mc² -- there is an incorrect space before the superscript 2. I thus suggest a command \concat wh

\concat markup command

2006-11-11 Thread Werner LEMBERG
All markup commands which accept more than a single markup put spaces inbetween. However, sometimes this is not useful (for example, just look at the bad appearance of the E=mc² -- there is an incorrect space before the superscript 2. I thus suggest a command \concat which does the same as \line