On 3/31/2015 11:18 PM, Matt Welland wrote: > On Mon, Mar 30, 2015 at 10:57 PM, Vikrant Chaudhary > <vikr...@webstream.io> wrote: >> fossil clone --cheap file:///path/to/upstream.fossil new-project.fossil > > +1 I think I would use this feature should it ever come available. I > have 500M+ repos where a cheap clone would be quite nice to have. I > assume the feature would work whether the upstream fossil was read only > or not. The benefit would be a clone that takes a few seconds rather > than several minutes.
I'm thinking about how this could be used at my workplace. On some
projects we have shared computers called viewservers ("view" being a
ClearCase term) on which we create our sandboxes (again, CC term).
Switching to Fossil would mean each user getting his or her own copy of
the full repository which synchronizes with the master. Furthermore,
each user would need a separate copy for each viewserver because it's
best not to share SQLite databases through NFS. This will eat a LOT of
disk space.
If users could somehow share repositories without copying them in full,
that would help a lot.
A simple test showing how Fossil repositories cannot be shared is to
attempt running two [fossil open] commands simultaneously. With small
projects this is hard to do, but you can just hit Ctrl-Z during the
first to make it take as long as you want. With projects such as those
I work on, [fossil open] takes a few minutes because (1) there's
gigabytes of stuff being written out, and (2) we're always stuck with
obsolete computers. So sharing any given repository file is clearly out
of the question.
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
