git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Franck <vagabon.xyz@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [QUESTION] Access to a huge GIT repository.
Date: Thu, 17 Nov 2005 11:36:47 +0100	[thread overview]
Message-ID: <cda58cb80511170236p4a7e2baay@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0511160837000.13959@g5.osdl.org>

Hi Linus

2005/11/16, Linus Torvalds <torvalds@osdl.org>:
>
>
> First off, "rsync://" will never do what you want. It uses rsync
> (surprised surprise) to grab the objects, so since it has no clue what the
> objects are, it has no choice but to just grab them all.
>

yes that was a bad example, actually I've tried several protocol
including git protocol.

> The fact that _some_ of the linux-mips repositories are based on mine
> makes me suspect that all their 2.6-based ones are rooted like mine is,
> but that may or may not be true.
>

hmm, don't think "linux mips" repository is rooted like yours. It
seems that it has been imported from mips cvs repository which
contains linux-mips history since 1995.

> Just try your above command line with "git://" instead.
>
> (NOTE! Doing a full clone like the above is pretty expensive with git for
> the server side, so it might take a while before it starts feeding you
> stuff if it is under heavy load)
>

well I've already tried that but have renounced after waiting more
than 4 hours ! I don't know if the server was under heavy load or if
git protocol needs a lots of resources but it seems useless to setup a
git dameon on it...

> If you want to get rid of other branches, do:

Sorry, I forget to tell that I have already tried what you suggested
at first (except that I did not do a 'git repack -a -d') but it didn't
work out (and that the reason why I tried the "kill father object"
thing). Since I forgot the repack thing, I retried again, and it did
last more than 4 hours to cpmplete all git commands. After that I run
gitk --all to check that all old branch's objects have been removed
but I can see all of them.

I plan to take look at git code to understand how object removal is
done, but until this do you have any ideas why this fails ?

Thanks
--
               Franck

  reply	other threads:[~2005-11-17 10:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 12:24 [QUESTION] Access to a huge GIT repository Franck
2005-11-16 16:46 ` Linus Torvalds
2005-11-17 10:36   ` Franck [this message]
2005-11-17 16:23     ` Linus Torvalds
2005-11-17 21:47       ` Franck
2005-11-17 22:44         ` Linus Torvalds
2005-11-19 12:23           ` Franck
2005-11-19 12:45             ` Lukas Sandström
2005-11-19 20:42               ` Junio C Hamano
2005-11-19 17:56             ` Linus Torvalds
2005-11-19 19:52               ` Junio C Hamano
2005-11-21 20:11                 ` Franck
2005-11-21 20:45                   ` Junio C Hamano
2005-11-22  9:22                     ` Franck
2005-11-22  9:50                       ` Junio C Hamano
2005-11-22 10:40                         ` Franck
2005-11-22 17:06                           ` Junio C Hamano
2005-11-22 19:10                             ` Franck
2005-11-16 18:24 ` Junio C Hamano
2005-11-16 20:01   ` Martin Langhoff
2005-11-16 20:10     ` Linus Torvalds
2005-11-16 20:35     ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cda58cb80511170236p4a7e2baay@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).