Mark Phippard wrote:
> Molle Bestefich wrote:
> > Unless you think I'm being totally ridiculous, I'd appreciate if you
> > could show me how to clearly document your variant of checkout?
>
> Doesn't it just come down to how one defines a "new working copy"?
Not sure. For me, checkout implicitly means fresh working copy.
Try the documentation dance I did. If you can make a concise and
clear description for newbie CLI users, I'll shut my yap about my
approach being cleaner :-).
> In my particular case, I am interested in this for Subclipse and our
> Eclipse integration. When we do a checkout, we have to first let Eclipse
> create some local project structure. This can often include some of the
> same files that are going to be checked out from the repository. So we
> have to look at everything Eclipse created, see if it is in the
> repository, and then delete it before starting the checkout. This is not
> too big of a problem, but there is also another common scenario that is a
> problem. For various reasons, someone disconnects their local project
> from SVN or maybe they are just starting with SVN and already have a copy
> of their project. They then want to connect it to SVN. Since the CVS
> plugin that comes with Eclipse allows all of this, they expect our plugin
> to do so as well. We can't provide this feature because we have no way of
> turning their local project into a working copy.
Super, thanks a lot, that explanation really helps when trying to
understand what you'd like to do.
> With this change to checkout, I could just do a checkout right on top
> of the local project and let things work themselves out.
You could accomplish what you want just as easily with my approach, so
not much difference there.
> Command line users have expressed the same desire, it particularly comes
> up as projects such as KDE migrate from CVS to SVN and all of the
> developers around the world want to just convert their local CVS working
> copy over to an SVN working copy. Ideally, they would also like it to do
> this intelligently and skip the download process as much as possible, but
> we are deferring that idea for now.
Same as above.
> As John Peacock pointed out, it might make sense to require the use of
> --force or some other switch to get this behavior. We can deal with that
> once we have the primary functionality actually working.
I've no preference.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 18 18:05:01 2006