You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by jbeall <jb...@heraldic.us> on 2007/07/23 21:15:43 UTC
I would like to vote for issue 1328 -- in-place import feature
request
I see this was requested back in the pre-1.0 days, but it doesn't appear to
have gotten any interest since then... has the idea been abandoned? I would
find it extremely useful. At my workplace we have *tons* of code that is
not in a version control system of any kind, and it would be extremely
useful to be able to do in-place imports. I can't imagine we're that
unique--I've had too many conversations with devs at other shops that are in
a similar situation.
Import-Rename-Checkout works, but it would be a lot nicer to import things
in place.
Here's the issue link, and some of the details:
http://subversion.tigris.org/issues/show_bug.cgi?id=1328
* Summary: Import should have an option to create WC (was "cannot checkout
over previously imported tree")
Description: Opened: Fri May 23 21:30:00 -0700 2003 Sort by: Oldest
first | Newest first
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
------- Additional comments from Ben Collins-Sussman Mon Jun 23 20:06:31
-0700 2003 -------
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.
------- Additional comments from David Waite Tue Dec 30 10:29:57 -0700 2003
-------
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."
------- Additional comments from Karl Fogel Tue Jul 6 07:21:32 -0700 2004
-------
Fix summary.
------- Additional comments from Ben Reser Wed Jul 21 09:35:32 -0700 2004
-------
Someone got carried away with platform and OS again. This applies to All.
--
View this message in context: http://www.nabble.com/I-would-like-to-vote-for-issue-1328----in-place-import-feature-request-tf4132507.html#a11752949
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: I would like to vote for issue 1328 -- in-place import feature
request
Posted by jbeall <jb...@heraldic.us>.
Mark Phippard-3 wrote:
>
> On 7/23/07, jbeall <jb...@heraldic.us> wrote:
>> http://subversion.tigris.org/issues/show_bug.cgi?id=1328
>
> I am not even sure why that is still open. You can certainly do stuff
> like that today. If this is all new code, just create the folder for
> it in the repositry, then checkout that folder to the location where
> your code resides. You can then svn add + commit which will leave
> behind a working copy. This is even referred to as "In-place import"
> which is why I am surprised this issue exists.
>
Interesting; I had tried this already without seeing the FAQ (Nathan Kidd
referenced the FAQ for "in-place import" in a different reply), but I was
missing the "checkout" step. That was the key to getting a proper working
copy.
This all works and does exactly what I was hoping for. Thanks. However, I
do think it would be slick to combine this into a single "in-place import"
command of some type. Alternatively, perhaps TortoiseSVN (and/or other
tools) could provide one-click in-place importing, implemented via the
"create folder->checkout to existing folder->add->commit" method. Nothing
more than a convenience method, but convenience *is* nice!
Thanks for the pointers!
Mark Phippard-3 wrote:
>
> As of the next version, you can now even use svn checkout --force to
> checkout an actual code tree on top of another code tree. It will
> leave the files in place and slide the WC beneath it.
>
That will be a nice feature.
-Josh
--
View this message in context: http://www.nabble.com/I-would-like-to-vote-for-issue-1328----in-place-import-feature-request-tf4132507.html#a11754239
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: I would like to vote for issue 1328 -- in-place import feature request
Posted by Mark Phippard <ma...@gmail.com>.
On 7/23/07, jbeall <jb...@heraldic.us> wrote:
>
> I see this was requested back in the pre-1.0 days, but it doesn't appear to
> have gotten any interest since then... has the idea been abandoned? I would
> find it extremely useful. At my workplace we have *tons* of code that is
> not in a version control system of any kind, and it would be extremely
> useful to be able to do in-place imports. I can't imagine we're that
> unique--I've had too many conversations with devs at other shops that are in
> a similar situation.
>
> Import-Rename-Checkout works, but it would be a lot nicer to import things
> in place.
>
> Here's the issue link, and some of the details:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1328
I am not even sure why that is still open. You can certainly do stuff
like that today. If this is all new code, just create the folder for
it in the repositry, then checkout that folder to the location where
your code resides. You can then svn add + commit which will leave
behind a working copy. This is even referred to as "In-place import"
which is why I am surprised this issue exists.
As of the next version, you can now even use svn checkout --force to
checkout an actual code tree on top of another code tree. It will
leave the files in place and slide the WC beneath it.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: I would like to vote for issue 1328 -- in-place import feature
request
Posted by Nathan Kidd <na...@spicycrypto.ca>.
jbeall wrote:
> I see this was requested back in the pre-1.0 days, but it doesn't appear to
> have gotten any interest since then... has the idea been abandoned? I would
> find it extremely useful. At my workplace we have *tons* of code that is
> not in a version control system of any kind, and it would be extremely
> useful to be able to do in-place imports.
Does this not work for you?
http://subversion.tigris.org/faq.html#in-place-import
-Nathan
> I can't imagine we're that
> unique--I've had too many conversations with devs at other shops that are in
> a similar situation.
>
> Import-Rename-Checkout works, but it would be a lot nicer to import things
> in place.
>
> Here's the issue link, and some of the details:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1328
>
>
> * Summary: Import should have an option to create WC (was "cannot checkout
> over previously imported tree")
>
> Description: Opened: Fri May 23 21:30:00 -0700 2003 Sort by: Oldest
> first | Newest first
>
> 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
>
> ------- Additional comments from Ben Collins-Sussman Mon Jun 23 20:06:31
> -0700 2003 -------
>
> 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.
>
> ------- Additional comments from David Waite Tue Dec 30 10:29:57 -0700 2003
> -------
>
> 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."
>
> ------- Additional comments from Karl Fogel Tue Jul 6 07:21:32 -0700 2004
> -------
>
> Fix summary.
>
> ------- Additional comments from Ben Reser Wed Jul 21 09:35:32 -0700 2004
> -------
>
> Someone got carried away with platform and OS again. This applies to All.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org