From: iani <zannos@gmail.com>
To: git@vger.kernel.org
Subject: Re: pushing to a remote branch that one does not own
Date: Wed, 19 Jan 2011 14:28:39 -0800 (PST) [thread overview]
Message-ID: <1295476119964-5941621.post@n2.nabble.com> (raw)
In-Reply-To: <4D373AA2.7000501@seznam.cz>
Thanks a lot for the prompt answer. Following your advice I read the progit
online chapter about branches and it explained to me about git branch lilt
origin/lilt as Maaartin explains. So I am testing it now.
Thanks
Iannis Z.
--
View this message in context: http://git.661346.n2.nabble.com/pushing-to-a-remote-branch-that-one-does-not-own-tp5940751p5941621.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2011-01-19 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 18:16 pushing to a remote branch that one does not own iani
2011-01-19 19:25 ` Maaartin
2011-01-19 22:28 ` iani [this message]
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=1295476119964-5941621.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).