usability - Why doesn't svn import put the imported folder under version control? -


this has driven me insane in past. i'm more or less on now, in far i've figured out how import files, delete them (a true leap of faith - more cautious among may prefer move them), , check out repository same place. i'm still baffled why have every time decide put project under version control.

from http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html

note after import finished, original local directory not converted working copy. begin working on data in versioned fashion, still need create fresh working copy of tree.

... why? every time i've ever used import command it's been local directory was, point, personal 'working copy'. unusual?

i totally aggree on that, design decision: svn tried keep clean concept in initial design.

  • import moves data into repository
  • checkout creates working copy
  • update updates working copy
  • commit send changes working copy repository

these 4 basic operations strictly separated information flow: from repository or to repository

i ran exact difficulty on several trainings, therefore developed different approach: never use import, alway check out empty (parent-)folder , copy stuff working copy. let me preview result examining svn status before committing , means training attendees 1 commando less remember.

if experienecd enough, checkout empty folder directly to-be-imported directory , add files afterwards. svn not check out prefilled directory, can use --force persuade svn try it.


Comments

Popular posts from this blog

java - WrongTypeOfReturnValue exception thrown when unit testing using mockito -

php - Magento - Deleted Base url key -

android - How to disable Button if EditText is empty ? -