Gavin Lambert wrote:
> Quoth johann.petrak@gmail.com <mailto:johann.petrak@gmail.com>:
>> I think an "unversion" command should be a standard part of
>> subversion: it can easily
>> happen that one puts unwanted files or even directories in the
>> repository by accident
>> when a big project is initially added.
>> It would probably be best to have a command that by default does what
>> the workaround
>> of copy/svn delete/copyback does, with a --force option that in
>> addition removes the complete history of the file from the repository
>> (this would be good to have if by accident very large files or
>> directories got added).
>
> It's a bit late once it's already in the repository, but to avoid
> these sorts of things I simply never use 'svn import' -- instead I
> use 'svn mkdir' to create an empty folder, then checkout that folder
> into my existing source tree. (SVN won't barf as long as the folder
> in the repo is empty, or at least that there aren't any clashing
> files.) Then I can specifically 'svn add' whatever files I need,
> which (since I usually use TSVN) is as simple as clicking a checkbox
> at commit time.
Me, too. The confusing and sometimes difficult to predict appending of
directory names by the svn import operation have created some big messes
that have been awkward to clean up in my work.
> Even with the command-line client, you should be able to 'svn add .'
> or 'svn add *' to add everything (equivalent to an import) and then
> 'svn revert' those files that you *don't* want added. Easy, and you
> get to verify that you've selected the right set of files before
> finally committing.
Be careful of "svn add *" forgetting to add files starting with ".".. I've
been bitten by that one: "svn add ." is safer.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 22 10:50:56 2006