git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Franck <vagabon.xyz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [QUESTION] Access to a huge GIT repository.
Date: Tue, 22 Nov 2005 01:50:01 -0800	[thread overview]
Message-ID: <7vfyppf1va.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <cda58cb80511220122r76ca69a2y@mail.gmail.com> (vagabon.xyz@gmail.com's message of "Tue, 22 Nov 2005 10:22:46 +0100")

Franck <vagabon.xyz@gmail.com> writes:

> 2005/11/21, Junio C Hamano <junkio@cox.net>:
>> Franck <vagabon.xyz@gmail.com> writes:
>>
>> > ... But since I used grafting to "cut"
>> > my light repo and .git/info/grafts file is not copied during
>> > push/pull/clone operations it's not going to work. Is it a scheme that
>> > could work ?
>>
>> If you tell your downloaders that your repository is incomplete
>> and they need to have at least up to such and such commits from
>> another repository, they should be able to slurp from you.

I was not talking about _your_ case specifically.  If you happen
to have based your partial history on top of a single commit
then the set of "such and such commits" might be only one, but
you could for example clone from Linus tip, merge in a couple of
jgarzik branch heads, put your own commits on top of them and
then cauterize your history, stopping at those foreign commits.
In such a case you obviously need to tell others where you
chopped your history off.

  reply	other threads:[~2005-11-22  9:50 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 [this message]
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

  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=7vfyppf1va.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=vagabon.xyz@gmail.com \
    /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).