From: Franck <vagabon.xyz@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [QUESTION] Access to a huge GIT repository.
Date: Tue, 22 Nov 2005 20:10:26 +0100 [thread overview]
Message-ID: <cda58cb80511221110i3d7ea4dj@mail.gmail.com> (raw)
In-Reply-To: <7v1x18fw8j.fsf@assigned-by-dhcp.cox.net>
2005/11/22, Junio C Hamano <junkio@cox.net>:
> Were you around on this list, around the beginning of this
> month?
nope, I subscribed to the list one week later.
> The thread that starts here may be of interest:
>
> http://marc.theaimsgroup.com/?l=git&m=113089701819420
>
> I think (although I do not exactly know how the "lite"
> repository was constructed) what you are doing is similar to
> what I called "shallow clone" there in that thread.
Indeed. What I'm doing to get my "shallow clone" is basicaly remove
every ref/branchs I don't want, then run git-prune, git-repack -a -d.
But the result should be the same as your "shallow clone" method.
> At the end
> of the thread I think I listed what you can and cannot do in
> such an incomplete repository.
>
Yes. But the big difference is that, in my case, the shallow copy is
used as a public repository, whereas in your case the shallow copy is
used as a working repository. Anyway, Ralf (the mips arch maintainer)
is going to create a new pruned repository that should resolve my
problem. I'm going to wait for it instead of trying to make my own
"broken" repository.
Thanks
--
Franck
next prev parent reply other threads:[~2005-11-22 19:10 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
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 [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cda58cb80511221110i3d7ea4dj@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).