From: Miles Bader <miles@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] deprecating and eventually removing "git relink"?
Date: Mon, 14 Nov 2011 15:06:37 +0900 [thread overview]
Message-ID: <buomxbzutjm.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <7v4ny7mtbx.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> (2) allowing two repositories that started independently to share objects
> using the alternates mechanism after the fact.
Can they not already?
I mean, it works great right now to do:
cd $REP2
echo $REP1/.git/objects > .git/objects/info/alternates
git gc
Do you mean a more elaborate UI that does this nicely...? or something
else?
It might be nice to have a mechanism where new objects would update
the _alternate_ rather than the object-store in the tree where the
command was run... then you could easily have a bunch of trees using a
central object store without needing to update the central store
occasionally by hand (and do gc in its "clients")...
-Miles
--
"Most attacks seem to take place at night, during a rainstorm, uphill,
where four map sheets join." -- Anon. British Officer in WW I
next prev parent reply other threads:[~2011-11-14 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 0:38 [RFC] deprecating and eventually removing "git relink"? Junio C Hamano
2011-11-14 6:06 ` Miles Bader [this message]
2011-11-14 6:27 ` Junio C Hamano
2011-11-14 9:03 ` Chris Packham
2011-11-14 8:48 ` Simon Brenner
2011-11-14 10:34 ` Jeff King
2011-11-14 20:18 ` Junio C Hamano
2011-11-14 20:25 ` Jeff King
2011-11-14 22:08 ` Junio C Hamano
2011-11-15 4:48 ` Miles Bader
2011-11-21 22:09 ` Phillip Susi
2011-11-21 22:19 ` Jeff King
2011-11-22 1:58 ` Phillip Susi
2011-11-14 10:24 ` Junio C Hamano
2011-11-15 4:40 ` Miles Bader
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=buomxbzutjm.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.