git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: pushing specific branches to a public mirror repos

From
Graeme Geldenhuys <graemeg@gmail.com>
Date
Jul 17, 2009, 09:11 UTC
Message-ID
<h3pf9d$mo7$1@ger.gmane.org>
In-Reply-To
<4A603B7A.6050208@viscovery.net>
Johannes Sixt wrote:
Show 5 quoted lines
> 
> 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/
Previous: Johannes SixtNext: Bert Wesarg
Message 3 of 5 in “pushing specific branches to a public mirror repos”
  1. Graeme GeldenhuysJul 17, 2009
  2. Johannes SixtJul 17, 2009
  3. Graeme GeldenhuysJul 17, 2009
  4. Bert WesargJul 17, 2009
  5. Johannes SixtJul 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.