[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1266 in lilypond: Dots in chords can not be moved

From: David Kastrup
Subject: Re: Issue 1266 in lilypond: Dots in chords can not be moved
Date: Sun, 30 Oct 2011 12:05:47 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux)

address@hidden writes:

> Comment #19 on issue 1266 by address@hidden: Dots in chords can not
> be moved
> http://code.google.com/p/lilypond/issues/detail?id=1266
> Hello, Yes I can do that - I need to get into the habit of the new workflow.
> Can I just check the command I need to use is:
> git push origin dev\staging
> and that is it - I don't want to break anything with my push access.
> Eg. I don't need to download a new repo just for dev/staging do I, I
> can just push from my own lilypond-git repo to dev/staging?

The command you need to use to push from HEAD is

git push origin HEAD:refs/heads/dev/staging

For some reason, sometimes the full ref on the right hand side is
required (probably when your repository does not know about staging
and/or you just deleted it).

You can't break anything in that manner: git will refuse to do anything
that is not an incremental addition to staging.  So dev/staging should
not be in a worse logical state than before, if your HEAD looks

Unfortunately, our repository is configured in a manner that you can't
convince git when an incremental addition is not possible (like when
there has been diverging stuff on master you want to rebase into
staging).  Instead you need to delete and rewrite dev/staging.  Deleting
it is done by doing the same push command, just without "HEAD" before
the colon.

But before you _rewrite_ dev/staging, better ask again.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]