From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Alternate object pool mechanism updates.
Date: Sun, 14 Aug 2005 18:53:02 -0700 [thread overview]
Message-ID: <7vr7cw7ypt.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508141726390.3553@g5.osdl.org> (Linus Torvalds's message of "Sun, 14 Aug 2005 17:29:05 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> I think this is great - especially for places like kernel.org, where a lot
> of repos end up being related to each other, yet independent.
Yes. There is one shortcoming in the current git-clone -s in
the proposed updates branch. If the parent repository has
alternates on its own, that information should be copied to the
cloned one as well (e.g. Jeff has alternates pointing at you,
and I clone from Jeff with -s flag --- I should list not just
Jeff but also you to borrow from in my alternates file).
> However, exactly for places like kernel.org it would _also_ be nice if
> there was some way to prune objects that have been merged back into the
> parent.
Yes. Another possibility is to use git-relink which was written
exactly to solve this in a different way.
next prev parent reply other threads:[~2005-08-15 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 9:09 [PATCH] Alternate object pool mechanism updates Junio C Hamano
2005-08-13 12:08 ` Petr Baudis
2005-08-13 18:33 ` Junio C Hamano
2005-08-14 23:46 ` Junio C Hamano
2005-08-15 0:29 ` Linus Torvalds
2005-08-15 1:53 ` Junio C Hamano [this message]
2005-08-16 19:07 ` Linus Torvalds
2005-08-16 19:45 ` Daniel Barkalow
2005-08-16 20:38 ` Junio C Hamano
2005-08-17 5:48 ` [PATCH] Use LF and allow comments in objects/info/alternates file Junio C Hamano
2005-08-16 21:47 ` [PATCH] Alternate object pool mechanism updates Junio C Hamano
2005-08-16 21:52 ` Linus Torvalds
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=7vr7cw7ypt.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--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).