On Tue, Aug 28, 2012 at 09:19:53PM +0200, Hallvard Breien Furuseth wrote:
Oswald Buddenhagen wrote:
(...)so the second approach is the bare aggregator repo which adds
all other repos as remotes, and the other repos link back via
alternates. problems:
- to actually share objects, one
Oswald Buddenhagen wrote:
(...)so the second approach is the bare aggregator repo which adds
all other repos as remotes, and the other repos link back via
alternates. problems:
- to actually share objects, one always needs to push to the aggregator
Run a cron job which frequently does that?
hi,
Junio C Hamano gitster at pobox.com writes:
The alternates mechanism [...]
sorry for the somewhat late response - i found this thread only now.
at qt-project.org we have a somewhat peculiar setup: we have the qt4 repository,
and a bunch of qt5 repositories which resulted from a split. qt5
Junio C Hamano wrote:
Some ideas:
- Make clone --reference without -s not to borrow from the
reference repository. (...)
Generalize: Introduce volatile alternate object stores. Commands like
(remote) fetch, repack, gc will copy desired objects they see there.
That allows
[..]
- By design, the borrowed object store MUST not ever lose any
object from it, as such an object loss can corrupt the borrowing
repositories. In theory, it is OK for the object store whose
objects are borrowed by repositories to acquire new objects, but
losing existing
On Sun, Aug 05, 2012 at 11:38:12AM +0200, Michael Haggerty wrote:
I have some other crazy ideas for making the concept even more powerful:
* Support remote alternate repositories. Local repository obtains
missing objects from the remote as needed. This would probably be
insanely
Junio C Hamano gits...@pobox.com writes:
- When you have one object store and a repository that does not yet
borrow from it, you may want to make the repository borrow from
the object store. Obviously you can run echo like the sample
script in the previous item above, but it is not
On 08/05/2012 06:56 AM, Junio C Hamano wrote:
The alternates mechanism [...]
The UI for this mechanism however has some room for improvement, and
we may want to start improving it for the next release after the
upcoming Git 1.7.12 (or even Git 2.0 if the change is a large one
that may be
Michael Haggerty mhag...@alum.mit.edu writes:
I have some other crazy ideas for making the concept even more powerful:
Sorry, but the a bit more sanity topic is not interested in making
the concept powerful at all.
This is about making it usable with ease without the user having to
worry about
9 matches
Mail list logo
