At 02:07 PM 12/07/2005 -0400, John Peacock wrote:
>Ben Collins-Sussman wrote:
>> Over and over, I see people get frustrated that after a large import
>> (or after a cvs2svn run) they're forced to run 'svn checkout', when the
>> original dataset is already sitting in front of them.
>
>This works really well for me:
>
> $ svk import --to-checkout . //depotpath
As I understand this, though, it doesn't apply to scenarios where projects
-- including their histories -- are imported using an external tool like
cvs2svn or vss2svn.
You mentioned that SVK can import directly from CVS repositories. Can it do
so from VSS or Perforce repositories as well? And, that aside, after
importing an external repository in that manner, you showed the use of a
command "svk sync". Does this command actually avoid the *network
bandwidth* of retrieving a revision from the SVN server? I couldn't see a
way to do that in the libsvn_ra interface, which I believe (perhaps
wrongly) to be representative of the functions available in the protocol.
Jonathan Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 13 01:05:34 2005