[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

AW: RE: RE: Feature Request

From: Andreas Rudischhauser <andreas.rudischhauser_at_back2.biz>
Date: 2007-04-24 10:18:12 CEST

If I copy somewhere back to the new checked out working copy and do then a commit, does subversion check, that not all files are "new"? How is this done? Via a hash code?

-----Ursprüngliche Nachricht-----
Von: Lübbe Onken [mailto:l.onken@rac.de]
Gesendet: Dienstag, 24. April 2007 10:02
An: 'users@tortoisesvn.tigris.org'
Betreff: RE: RE: Feature Request

Hi Andreas Rudischhauser,

You wrote:
> What is SVN co. I didn't find it in the help documents... or is co =
> commit?

This is command line client syntax
'co' stands for 'check out'
'ci' stands for 'check in / commit'

A bug in the script. The first line should read

> copy yourWC somewhere
move yourWC somewhere

> svn co yourURL yourWC
> copy somewhere yourWC

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Apr 24 10:20:22 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.