>> We will get around to optimising that case at some point, but it's a
>> rather low priority.
> That sounds great. Do you have a ticket tracking this in RT, or
> somewhere else I can follow any progress/get hints on where to look
> myself, if I ever get crazy^Wbrave enough to try that?
Please subscribe to darcs-devel. There's no particular ticket on this
subject, as it isn't a localised issue; we're getting at it by impro-
ving Darcs' behaviour bit by bit.
In the case of large initial imports, we discussed the possibility of
having a special hunk type optimised for this particular case. It's
not difficult to implement, would provide immediate benefits for Git
repos, but making best use of it will require an incompatible change
in the on-disk format for native Darcs repos.
> Where should I have used 'get' or 'put' instead?
You're right, you couldn't have in your case.
>> I have trouble believing that your 75MB are a single project
> I wouldn't want to question your beliefs, but a cvs checkout of
> COIN-OR is around 75MB.
`` The following is a list of projects currently being hosted by
COIN-OR, sorted by category:''
This is unfortunately a quite typical abuse of CVS. The same holds of
the XFree86 project, which I used to work on: 3 million lines of code
in a single CVS module.
> This was what the other part of my question was: How do I do this
> easily? ("Easily" meaning automatic here :-))
I'd do something like
$ darcs initialize
$ darcs add *
$ darcs record -a
$ for i in *; do
> if [ -d "$i" ]; then
> darcs add -r "$i"
> darcs record -a -m "Import of $i"
> fi
> done
but I'd do it manually, in order to make sure I'm committing in
logical chunks. (Committing in logical chunks buys you the possibi-
lity of splitting the repository later on, if you know what you're
doing.)
> What is a binary commit? Where can I read about this?
See ``binaries'' under ``prefs'' under ``Configuring darcs'' in the
Darcs manual.
Binaries are treated as opaque blobs of bytes; they get none of Darcs'
merging functionality, but they are much faster.
You should use binary imports for all non-text files in your reposi-
tory, but you may also use them for any large files that you don't
plan on modifying.
Juliusz
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
