You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Philip Martin <ph...@codematters.co.uk> on 2002/05/02 21:37:11 UTC
Should checkout into a working copy fail?
Hello
Earlier today I confidently stated that subversion doesn't support
multiple checkouts of different URLs into the same directory. Trying
it, I find that svn will often allow the checkouts, and that only at
update, or worse commit, does an error occur. Am I right to say that
multiple checkouts into the same directory are not supported, or are
there any circumstances under which it ought to work?
Assuming it isn't supported, I have a simple patch that prohibits all
checkouts into a working copy.
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Should checkout into a working copy fail?
Posted by Philip Martin <ph...@codematters.co.uk>.
Ben Collins-Sussman <su...@collab.net> writes:
> Philip Martin <ph...@codematters.co.uk> writes:
>
> > > I can remember back in the earliest days of coding, when we were first
> > > writing the update-editor, that we were checking to prevent writing to
> > > an existing WC. How the heck did we lose this check?
> >
> > Uh, no regression test? I wrote one of those as well :)
> >
>
> Are you kiddin? That "existing-WC" check was built into the earliest
> foundations of the update-editor. Eons ago it was, in the Elder Days.
> When the world was grey, long before there were tests of any kind. :-)
$ rm -rf ~/wc
$ svn co file:///home/pm/repo -d ~/wc
A /home/pm/wc/trunk
A /home/pm/wc/trunk/foo
A /home/pm/wc/trunk/bar
A /home/pm/wc/trunk/zig
A /home/pm/wc/trunk/zig/zag
A /home/pm/wc/branch
A /home/pm/wc/branch/foo
Checked out revision 7.
$ svn co file:///home/pm/repo/trunk -d ~/wc
A /home/pm/wc/foo
A /home/pm/wc/bar
A /home/pm/wc/zig
A /home/pm/wc/zig/zag
Checked out revision 7.
$ echo x >> ~/wc/zig/zag
$ svn st -uv ~/wc
_ 7 7 pm /home/pm/wc
_ 7 6 pm /home/pm/wc/bar
_ 7 5 pm /home/pm/wc/branch
_ 7 5 pm /home/pm/wc/branch/foo
_ 7 4 pm /home/pm/wc/foo
_ 7 7 pm /home/pm/wc/trunk
_ 7 6 pm /home/pm/wc/trunk/bar
_ 7 4 pm /home/pm/wc/trunk/foo
_ 7 7 pm /home/pm/wc/trunk/zig
_ 7 7 pm /home/pm/wc/trunk/zig/zag
_ 7 7 pm /home/pm/wc/zig
M 7 7 pm /home/pm/wc/zig/zag
Head revision: 7
$ svn ci ~/wc
Sending wc/zig/zag
../svn/subversion/libsvn_client/commit.c:602
svn_error: #21062 : <Filesystem has no such file>
Commit failed (details follow):
../svn/subversion/libsvn_fs/tree.c:180
svn_error: #21062 : <Filesystem has no such file>
file not found: transaction `26', path `/zig/zag'
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Should checkout into a working copy fail?
Posted by Ben Collins-Sussman <su...@collab.net>.
Philip Martin <ph...@codematters.co.uk> writes:
> > I can remember back in the earliest days of coding, when we were first
> > writing the update-editor, that we were checking to prevent writing to
> > an existing WC. How the heck did we lose this check?
>
> Uh, no regression test? I wrote one of those as well :)
>
Are you kiddin? That "existing-WC" check was built into the earliest
foundations of the update-editor. Eons ago it was, in the Elder Days.
When the world was grey, long before there were tests of any kind. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Should checkout into a working copy fail?
Posted by Philip Martin <ph...@codematters.co.uk>.
Ben Collins-Sussman <su...@collab.net> writes:
> Philip Martin <ph...@codematters.co.uk> writes:
>
> > Assuming it isn't supported, I have a simple patch that prohibits all
> > checkouts into a working copy.
>
> Guh?!?!?
>
> I can remember back in the earliest days of coding, when we were first
> writing the update-editor, that we were checking to prevent writing to
> an existing WC. How the heck did we lose this check?
Uh, no regression test? I wrote one of those as well :)
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Should checkout into a working copy fail?
Posted by Ben Collins-Sussman <su...@collab.net>.
Philip Martin <ph...@codematters.co.uk> writes:
> Assuming it isn't supported, I have a simple patch that prohibits all
> checkouts into a working copy.
Guh?!?!?
I can remember back in the earliest days of coding, when we were first
writing the update-editor, that we were checking to prevent writing to
an existing WC. How the heck did we lose this check?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Should checkout into a working copy fail?
Posted by Karl Fogel <kf...@newton.ch.collab.net>.
Philip Martin <ph...@codematters.co.uk> writes:
> Earlier today I confidently stated that subversion doesn't support
> multiple checkouts of different URLs into the same directory. Trying
> it, I find that svn will often allow the checkouts, and that only at
> update, or worse commit, does an error occur. Am I right to say that
> multiple checkouts into the same directory are not supported, or are
> there any circumstances under which it ought to work?
>
> Assuming it isn't supported, I have a simple patch that prohibits all
> checkouts into a working copy.
It's not supposed to be supported yet. What's that patch? :-)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org