git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: iani <zannos@gmail.com>
To: git@vger.kernel.org
Subject: pushing to a remote branch that one does not own
Date: Wed, 19 Jan 2011 10:16:51 -0800 (PST)	[thread overview]
Message-ID: <1295461011273-5940751.post@n2.nabble.com> (raw)


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
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? 

Thanks, 

Iannis Zannos


-- 
View this message in context: http://git.661346.n2.nabble.com/pushing-to-a-remote-branch-that-one-does-not-own-tp5940751p5940751.html
Sent from the git mailing list archive at Nabble.com.

             reply	other threads:[~2011-01-19 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 18:16 iani [this message]
2011-01-19 19:25 ` pushing to a remote branch that one does not own Maaartin
2011-01-19 22:28   ` iani
2011-01-19 19:56 ` Alexey Shumkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1295461011273-5940751.post@n2.nabble.com \
    --to=zannos@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).