Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-1328

Import should have an option to create WC (was "cannot checkout over previously imported tree")

        Details

        • Type: Improvement
        • Status: Resolved
        • Priority: Minor
        • Resolution: Fixed
        • Affects Version/s: all
        • Fix Version/s: 1.5.0
        • Component/s: libsvn_client
        • Labels:
          None

          Description

          This is useful when you want to create a project in an IDE and them
import it. The .svn dir is needed so a fresh checkout or even a way to
do an import that writes back the .svn dirs would be great.

Thanks

          Original issue reported by dbradby

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            sussman Ben Collins-Sussman added a comment - 

            I'm not sure whether even *CVS* allows you to do a 'checkout' which
overwrites an unversioned tree.  The idea makes my skin crawl. 
Assigning to post-1.0, enhancement.  Let the debate over this happen
later.

            Show
            sussman Ben Collins-Sussman added a comment - I'm not sure whether even *CVS* allows you to do a 'checkout' which overwrites an unversioned tree. The idea makes my skin crawl. Assigning to post-1.0, enhancement. Let the debate over this happen later.
            Hide
            Permalink
            subversion-importer Subversion Importer added a comment - 

            Copy of text sent to the mailing list:

"Just a $0.02 on this subject - my ideal 'import' would actually just be a svn add which did not 
require a root wc. it would schedule the whole imported tree for addition, and perhaps would scan 
for things such as mime-type and line endings and set those properties. However, it wouldn't 
affect the repository until I did a commit. This would allow me to have much stronger control over 
my imports, and also would leave me after import with a valid working copy."

            Original comment by akuma

            Show
            subversion-importer Subversion Importer added a comment - Copy of text sent to the mailing list: "Just a $0.02 on this subject - my ideal 'import' would actually just be a svn add which did not require a root wc. it would schedule the whole imported tree for addition, and perhaps would scan for things such as mime-type and line endings and set those properties. However, it wouldn't affect the repository until I did a commit. This would allow me to have much stronger control over my imports, and also would leave me after import with a valid working copy." Original comment by akuma
            Hide
            Permalink
            kfogel Karl Fogel added a comment - 

            Fix summary.

            Show
            kfogel Karl Fogel added a comment - Fix summary.
            Hide
            Permalink
            breser Ben Reser added a comment - 

            Someone got carried away with platform and OS again.  This applies to All.

            Show
            breser Ben Reser added a comment - Someone got carried away with platform and OS again. This applies to All.
            Hide
            Permalink
            subversion-importer Subversion Importer added a comment - 

            Is there any likelihood this will ever make it into subversion?

I've lately had to explain to a number of people new to subversion that after
they have checked in they need to immediately checkout - it always results in a
look of surprise and confusion.

I usually work in eclipse (using the subclipse plugin).  Importing a project
with subclipse does result in the copy i'm importing becoming the working copy,
which begs the question: how does subclipse handle this?  Does it automagically
delete the old copy and checkout a new copy?

            Original comment by steveliles

            Show
            subversion-importer Subversion Importer added a comment - Is there any likelihood this will ever make it into subversion? I've lately had to explain to a number of people new to subversion that after they have checked in they need to immediately checkout - it always results in a look of surprise and confusion. I usually work in eclipse (using the subclipse plugin). Importing a project with subclipse does result in the copy i'm importing becoming the working copy, which begs the question: how does subclipse handle this? Does it automagically delete the old copy and checkout a new copy? Original comment by steveliles
            Hide
            Permalink
            subversion-importer Subversion Importer added a comment - 

            Useful link from the FAQ, in case someone arrives at this bug, as I did, from a
google search.

http://subversion.tigris.org/faq.html#in-place-import

            Original comment by steveliles

            Show
            subversion-importer Subversion Importer added a comment - Useful link from the FAQ, in case someone arrives at this bug, as I did, from a google search. http://subversion.tigris.org/faq.html#in-place-import Original comment by steveliles
            Hide
            Permalink
            dlr Daniel Rall added a comment - 

            In Subversion 1.5, 'svn remove' has grown a --keep-local argument.  Adding
something like that to 'checkout' might work here.

            Show
            dlr Daniel Rall added a comment - In Subversion 1.5, 'svn remove' has grown a --keep-local argument. Adding something like that to 'checkout' might work here.
            Hide
            Permalink
            cmpilato C. Michael Pilato added a comment - 

            I thought this was exactly what Subversion 1.5's 'svn checkout --force' was for?

            Show
            cmpilato C. Michael Pilato added a comment - I thought this was exactly what Subversion 1.5's 'svn checkout --force' was for?
            Hide
            Permalink
            dlr Daniel Rall added a comment - 

            Yup, I think you're right -- that's a sufficient work-around for this issue.

            Show
            dlr Daniel Rall added a comment - Yup, I think you're right -- that's a sufficient work-around for this issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                subversion-importer Subversion Importer
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development