VCS: Proposal for a change of arguments to remove(), checkout() and import()

[Matthew Woehlke]

(Yes, I'm ludicrously behind on mail. Sorry.)

Fabian Wiesel wrote:
> This may be a reason why VcsMapping came into existence, but it doesn't
> negate the problems I cited.
> What does one gain by batching all the checkouts? And is it sensible to
> require all but one VCS to re-implement said capability?

How would you implement perforce-like semantics otherwise? Hmm, I guess 
Andreas answered that.

@Andreas: yes, you can (with perforce) check out bits from different 
branches.

Basically, perforce doesn't work as "clone a directory", it works with 
"client specifications", which consist of a working copy root and a list 
of mappings between repo and local checkout. For what I work with, it's 
common for a perforce client spec to have several entries, sometimes dozens.

(Actually, I wonder, is this useful for git submodules also?)

-- 
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
-- 
A KWin crash is like a Finite Improbability Generator... only instead of 
undergarments, all my windows move 4 pixels to the right.