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

Re: Pushing to GitHub doesn't push all branches

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Jul 10, 2009, 14:58 UTC
Message-ID
<4A575711.1050007@drmicha.warpmail.net>
In-Reply-To
<4A575416.2090304@drmicha.warpmail.net>

Michael J Gruber venit, vidit, dixit 10.07.2009 16:45: ...

> I think what you really want is to push everything under remote
> (assuming there are only svn branches) into proper heads on github, i.e.
> a refspec like '+refs/remotes/*:refs/*' for your pushes.
Uhm, make that '+refs/remotes/*:refs/heads/*' ;)
Previous: Michael J GruberNext: Graeme Geldenhuys
Message 3 of 8 in “Pushing to GitHub doesn't push all branches”
  1. Graeme GeldenhuysJul 10, 2009
  2. Michael J GruberJul 10, 2009
  3. Michael J GruberJul 10, 2009
  4. Graeme GeldenhuysJul 10, 2009
  5. Michael J GruberJul 10, 2009
  6. Graeme GeldenhuysJul 13, 2009
  7. Michael J GruberJul 13, 2009
  8. Graeme GeldenhuysJul 13, 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.