From: "Carlos Martín Nieto" <cmn@elego.de>
To: Srinidhi K V <srinidhikv@yahoo.co.in>
Cc: git@vger.kernel.org
Subject: Re: Unable to push remote branches
Date: Fri, 6 May 2011 10:30:03 +0200 [thread overview]
Message-ID: <20110506083003.GA6866@bee.lab.cmartin.tk> (raw)
In-Reply-To: <BANLkTimd887k0D=OL9rSuq6Z3FkhNAFAbQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
On Fri, May 06, 2011 at 10:17:37AM +0530, Srinidhi K V wrote:
> Hi All,
>
> I have a GIT repository in which there are lot of remote branches, I
> have created a bare git repository in my server. When I push my local
> repository to the bare repository in server using "git push --all"
> only local branches get pushed.
This is exactly what the man page says --all does. Remote branches are
under refs/remotes/<remote>/heads. You might want to use --mirror or
specify refs/remotes/* as the branches to push (I haven't tested this
refspec, but I think it should work).
cmn
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-05-06 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 4:47 Unable to push remote branches Srinidhi K V
2011-05-06 8:30 ` Carlos Martín Nieto [this message]
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=20110506083003.GA6866@bee.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=srinidhikv@yahoo.co.in \
/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).