2009/12/16 John A Meinel <email address hidden>:
> A lightweight checkout doesn't have any history locally, so it has to. I
> suppose one option would be to have export see what files are locally
> modified, and use the wt for unchanged files, and fall back to the
> repository for the rest. That would complicate the code a fair amount,
> though.
If we do this, I'd suggest not putting it into export, but rather into
the DirstateRevisionTree (or whatever it's called). Some care may be
needed to make sure there is no race between checking the file is
unmodified and actually reading it. But it's possible.
2009/12/16 John A Meinel <email address hidden>:
> A lightweight checkout doesn't have any history locally, so it has to. I
> suppose one option would be to have export see what files are locally
> modified, and use the wt for unchanged files, and fall back to the
> repository for the rest. That would complicate the code a fair amount,
> though.
If we do this, I'd suggest not putting it into export, but rather into nTree (or whatever it's called). Some care may be
the DirstateRevisio
needed to make sure there is no race between checking the file is
unmodified and actually reading it. But it's possible.
-- launchpad. net/~mbp/>
Martin <http://