Hi, On Tue, 30 Oct 2007, Rune Zedeler wrote:
> Johannes Schindelin skrev: > > > The workaround, then, to force a non-fast-forwarding push is > > > > # delete the branch on the remote > > $ git push <remote> :rune > > $ git push ssh+git://[EMAIL PROTECTED]/srv/git/lilypond.git/ :dev/rune > error: src refspec does not match any. > fatal: The remote end hung up unexpectedly > $ Ouch. How old is the installation on git.sv.gnu.org? This behaviour has been part of git since version 1.5.0-rc0. FYI, 1.5.0 came out on Feb 14, this year. > > # push the "new" branch > > $ git push <remote> rune > > > > But please be aware of the implications whenever you do something like > > that! > > Yeah, I really messed it up, I know. I had misunderstood how to work > with git. It was a mistake to merge with master branch. Hmm. So I really can only suggest to fork lilypond.git on repo.or.cz. There you really have control over _your_ repository. Ciao, Dscho _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
