I am confused. I have created the revision library with sparse and greedy options, changed a single line in a single file, and I am 5 minutes down my commit still waiting on "update pristine tree ..." with billions of disk access so I can barely do anything else on my laptop.
OK , now it is done : 6 minutes for 1 file ? I know I can commit a single file separately, but what about a directory ? It took 10 minutes to add 10 files and commit. Also, after my commit, there is a new revision but it is not added to the library. Do I need to add it by hand ? Does arch scale up to big projects with this patch applying mechanism ? Thanks, Philippe On Tue, 2005-08-23 at 09:42 +0200, Matthieu Moy wrote: > "Philippe Moutarlier" <[EMAIL PROTECTED]> writes: > > > Is that the only way to get decent speed ? Then I guess it is not an > > option for us. > > The main interesting idea that I was trying to sell is the ability to do > > remote software version management while not being connected to the > > network. This is especially interesting for people on the road with > > their laptops who could not afford to store revision libraries. > > Revision libraries are a solution for disconnected operations, not a > problem. Commands like "baz status", "baz diff" do not need access to > the archive if the revision library is filled in. If you need to be > able to commit offline, then branch in your local archive and merge > when you come back on the network. > > Unless you have very limited disk space on your laptops, I'm pretty > sure you can afford to store revision libraries (configured with > --sparse --greedy). You'll just need to prune it from time to time (rm > -fr some revision directory, or use the script provided in tla-tools). > _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
