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

Local branch to remote branch translation

From
Jon Smirl <jonsmirl@gmail.com>
Date
Nov 11, 2007, 17:54 UTC
Message-ID
<9e4733910711110954m3ed3f9adtf19ca15dff61f0@mail.gmail.com>
What am I doing wrong in this sequence?
In my local repo I have two remotes:

jonsmirl@terra:~/mpc5200b$ git remote dreamhost linus

I create branches off from these using: git branch -b m29 linus/master

I update them with stg rebase linus/master

My repo has a .git/packed-refs file
When I push this repo to a remote server my local branches get renamed.
jonsmirl@terra:~/mpc5200b$ git push dreamhost
To ssh://jonsmirl1@git.digispeaker.com/~/mpc5200b.git
 * [new branch]      m24 -> linus/m24
 * [new branch]      m25 -> linus/m25
 * [new branch]      m26 -> linus/m26
 * [new branch]      m28 -> linus/m28
 * [new branch]      m29 -> linus/m29
Counting objects: 619084, done.
...
So one the remote server I see this:
[daedalus]$ git remote
[daedalus]$ git branch
[daedalus]$ git branch -r
  linus/m24
  linus/m25
  linus/m26
  linus/m28
  linus/m29
[daedalus]$

With the repo in this state at the remote server gitweb thinks the repo is empty. Why are these branches getting renamed?

git head is in use on both ends.
-- 
Jon Smirl
jonsmirl@gmail.com
Next: Jon Smirl
Message 1 of 10 in “Local branch to remote branch translation”
  1. Jon SmirlNov 11, 2007
  2. Jon SmirlNov 11, 2007
  3. Steffen ProhaskaNov 11, 2007
  4. Jon SmirlNov 11, 2007
  5. Steffen ProhaskaNov 11, 2007
  6. Jon SmirlNov 11, 2007
  7. Steffen ProhaskaNov 11, 2007
  8. Jon SmirlNov 11, 2007
  9. Steffen ProhaskaNov 12, 2007
  10. Jon SmirlNov 12, 2007

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.