On 1/2/11 08:27, "Konstantin Khomoutov" <flatw...@users.sourceforge.net>
> On Mon, 31 Jan 2011 21:25:31 +0100
> Karel Vervaeke <ka...@vervaeke.info> wrote:
> (Formatting sanitized.)
>>>> I can see various possible ways this might work, but I can't afford
>>>> to get it wrong, so I'd be grateful for a nudge in the right
>>> $ git push REMOTE D:REMOTE_BRANCH
>>> REMOTE is the name of the remote repository,
>>> D is SHA-1 (or another name) of the specific commit you want to
>>> push, REMOTE_BRANCH is the branch you want to update.
>> Another approach would be to create another local branch containing
>> only A B C D and then pushing that branch.
> Strictly speaking that approach would not be different as the whole
> reason for such a branch to exist in this case would be to use its name
> in the git-push invocation; I referred to this using the "or another
> name" phrase.
> A tag would do as well, as E^ would, and so on according to the
> "gitrevisions" manual page.
Thanks for the advice. I was working on the right lines, but it's good to
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at