Re: pushing to a remote branch that one does not own

From: Maaartin <grajcar1@seznam.cz>
Date: Jan 19, 2011, 19:25 UTC
Message-ID: <4D373AA2.7000501@seznam.cz>
In-Reply-To: <1295461011273-5940751.post@n2.nabble.com>

On 11-01-19 19:16, iani wrote:

Show 18 quoted lines

>
> Hello,
> I want to contribute via "push" to a branch which I have previously cloned
> from a remote repository. There is a problem:
>
> If i create a new commit on branch "master", which coincides with
> origin/master, then I can push this commit simply with
>     git push
> However, if i switch to a different branch of the repository which was
> cloned, for example by doing:
>     git checkout origin/lilt
> Then I get the message:
> "You are in 'detached HEAD' state. You can look around, make experimental
> ... (etc)"
> So I HAVE to create my own new branch based on the one downloaded in order
> to start committing and pushing changes. My question is therefore:
>
> Am I strictly limited to committing only on the master / origin/master

AFAIK, there's nothing special about origin, except that it's already set up to track origin/master.

You can't commit to origin/lilt just like you can't commit to origin/master. Those remote branches are there to mirror corresponding branches in the remote repo, so you can do things like git diff master origin/master

> branched, and forced to make a new branch for every branch that I cloned
> from the remote repo, or is there a way of making the heads of the remote
> branches visible as local too?

AFAIK, using git branch lilt origin/lilt you create a local branch tracking the remote one. Then you can work with it just like you work with master. You may want to have a look at .git/config for [branch <branchname>] sections or not. I'm quite a newbie, but this works for me.