From: Graeme Geldenhuys <graemeg@gmail.com>
To: git@vger.kernel.org
Subject: Re: pushing specific branches to a public mirror repos
Date: Fri, 17 Jul 2009 11:11:59 +0200 [thread overview]
Message-ID: <h3pf9d$mo7$1@ger.gmane.org> (raw)
In-Reply-To: <4A603B7A.6050208@viscovery.net>
Johannes Sixt wrote:
>
> You can have more than one push line in the config:
>
> push = +refs/remotes/trunk:refs/heads/trunk
> push = +refs/remotes/fixes_2_2:refs/heads/fixes_2_2
Excellent, thanks. I thought about that, but wasn't sure and did not
want to try because I already screwed up the GitHub mirror once before.
> push = +refs/remotes/trunk:refs/heads/trunk
Must this stay as is, or must I push 'remotes/trunk' to 'heads/master'?
push = +refs/remotes/trunk:refs/heads/trunk
vs
push = +refs/remotes/trunk:refs/heads/master
From my server...
$ git ls-remote github
6b9b6460aa79a4b86c6bb1535b78e4fc555f89d5 HEAD
6b9b6460aa79a4b86c6bb1535b78e4fc555f89d5 refs/heads/master
My local "master" branch is currently tracking the refs/remotes/trunk,
but for some reason (which I don't understand), if I do a 'git svn
fetch' by default master branch is not updated. I still have to run 'git
svn rebase -l' to get master in sync. Is there something I can change in
the config to automate that as well?
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net/fpgui/
next prev parent reply other threads:[~2009-07-17 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 8:30 pushing specific branches to a public mirror repos Graeme Geldenhuys
2009-07-17 8:51 ` Johannes Sixt
2009-07-17 9:11 ` Graeme Geldenhuys [this message]
2009-07-17 9:47 ` Bert Wesarg
2009-07-17 10:05 ` Johannes Sixt
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='h3pf9d$mo7$1@ger.gmane.org' \
--to=graemeg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.