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

How to fork on repo.or.cz?

From
Dmitrijs Ledkovs <dmitrij.ledkov@ubuntu.com>
Date
Apr 24, 2010, 19:33 UTC
Message-ID
<x2r86ecb3c71004241233h97e3cf08l89aa4e6ef2fc4425@mail.gmail.com>
Hi all,
I'm not sure if it is bug on repo.or.cz or I'm doing something wrong.

Here (gitweb url) http://repo.or.cz/w/binutils.git is a clone of binutils git-cvsimport I've made a fork of that repo (gitweb url) http://repo.or.cz/w/binutils/xnox.git

>From the fork website I'm folling the instructions:
"$ git clone --reference /path/to/your/binutils.git/incarnation mirror_URL"

So I do this: $ git clone git://repo.or.cz/binutils.git --reference ~/src/cross/binutils.git/

And I get repo very quickly cause objects are reused. Then I try to do this:

$ cd binutils/ $ git push ssh://repo.or.cz/srv/git/binutils/xnox.git --all Counting objects: 178357, done. Delta compression using up to 2 threads. Compressing objects: 100% (36896/36896), done. ^Citing objects: 5% (8918/178357), 2.16 MiB | 483 KiB/s

I terminate that, because my expectation is that repo:binutils/xnox.git has access to all objects in repo:binutils.git and should IMHO nearly instantly creates refs for all branches cause nothing changed. Looking at this output it doesn't seem like my fork is reusing objects from the "fork parent" repo.

What wrong? How am I suppose to use forks on repo.or.cz such that I upload just *my* commits and don't re-upload whole history again.

Please help
Thanks.
Next: Jason Merrill
Message 1 of 3 in “How to fork on repo.or.cz?”
  1. Dmitrijs LedkovsApr 24, 2010
  2. Jason MerrillMay 6, 2010
  3. Dmitrijs LedkovsMay 6, 2010

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.