git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* How to fork on repo.or.cz?
@ 2010-04-24 19:33 Dmitrijs Ledkovs
  2010-05-06  4:38 ` Jason Merrill
  0 siblings, 1 reply; 3+ messages in thread
From: Dmitrijs Ledkovs @ 2010-04-24 19:33 UTC (permalink / raw)
  To: git

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-05-06  9:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-24 19:33 How to fork on repo.or.cz? Dmitrijs Ledkovs
2010-05-06  4:38 ` Jason Merrill
2010-05-06  9:51   ` Dmitrijs Ledkovs

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).