You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jason Winnebeck <jp...@rit.edu> on 2007/07/11 19:01:54 UTC
Single commit multiple WCs?
If I have multiple WCs, is it possible to do a copy/move between them or
a commit between them? They are from the same repository.
I have a repository structure like so:
AppA
- branches/tags/trunk
AppB
- branches/tags/trunk
LibA
- branches/tags/trunk
LibB
- branches/tags/trunk
LibC
- branches/tags/trunk
...
The dependencies don't form a tree, which is why they are in separate
modules like above. Doing it this way keeps everyone from needing to get
every directory, so let's say a developer of project A might have 3
separate checkouts:
/Dev
- /AppA (from AppA/trunk)
- /LibA (from LibA/trunk)
- /LibB (from LibB/trunk)
With this directory layout, does this mean it is impossible to do an
atomic commit that changes AppA and LibA at the same time? I noticed
from /Dev I can do a svn mv between two working copies, but of course I
cannot do a svn commit from /Dev, so the move cannot be atomic. Is there
a way I can organize it better? It seems unreasonable to have people
check out from a higher level as they will get the entire repository. Or
is the solution in this case just to "deal with it" -- each project is
conceptually separate so their commits will not be intermixed?
Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Single commit multiple WCs?
Posted by Mark Phippard <ma...@gmail.com>.
On 7/11/07, Matthew Hannigan <ml...@zip.com.au> wrote:
> On Wed, Jul 11, 2007 at 03:06:32PM -0400, Mark Phippard wrote:
> > > [ ... ]
> > >The dependencies don't form a tree, which is why they are in separate
> > >modules like above. Doing it this way keeps everyone from needing to get
> > >every directory, so let's say a developer of project A might have 3
> > >separate checkouts:
> > >
> > >/Dev
> > > - /AppA (from AppA/trunk)
> > > - /LibA (from LibA/trunk)
> > > - /LibB (from LibB/trunk)
> > > [ ... ]
>
> > See this issue:
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=2381
> >
> > It includes a link to a hacky workaround. Basically checkout an empty
> > folder somewhere and copy its .svn folder to /Dev. This gets by the
> > checking that SVN does to see if there is a common WC.
>
> Curiously enough I get commits from Eclipse users which have commits
> from different WCs (projects in eclipse parlance)
>
> I guess Eclipse (well, actually subclipse) must do something like the
> hacky workaround automatically?
The next major Subclipse release will do the hacky workaround. The
current version it works for people that choose to use the pure Java
SVNKit client option. That has a method that handle this situation
and Subclipse is coded to use that method when SVNKit is used.
--
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: Single commit multiple WCs?
Posted by Matthew Hannigan <ml...@zip.com.au>.
On Wed, Jul 11, 2007 at 03:06:32PM -0400, Mark Phippard wrote:
> > [ ... ]
> >The dependencies don't form a tree, which is why they are in separate
> >modules like above. Doing it this way keeps everyone from needing to get
> >every directory, so let's say a developer of project A might have 3
> >separate checkouts:
> >
> >/Dev
> > - /AppA (from AppA/trunk)
> > - /LibA (from LibA/trunk)
> > - /LibB (from LibB/trunk)
> > [ ... ]
> See this issue:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=2381
>
> It includes a link to a hacky workaround. Basically checkout an empty
> folder somewhere and copy its .svn folder to /Dev. This gets by the
> checking that SVN does to see if there is a common WC.
Curiously enough I get commits from Eclipse users which have commits
from different WCs (projects in eclipse parlance)
I guess Eclipse (well, actually subclipse) must do something like the
hacky workaround automatically?
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Single commit multiple WCs?
Posted by Mark Phippard <ma...@gmail.com>.
On 7/11/07, Jason Winnebeck <jp...@rit.edu> wrote:
> If I have multiple WCs, is it possible to do a copy/move between them or
> a commit between them? They are from the same repository.
>
> I have a repository structure like so:
>
> AppA
> - branches/tags/trunk
> AppB
> - branches/tags/trunk
> LibA
> - branches/tags/trunk
> LibB
> - branches/tags/trunk
> LibC
> - branches/tags/trunk
> ...
>
> The dependencies don't form a tree, which is why they are in separate
> modules like above. Doing it this way keeps everyone from needing to get
> every directory, so let's say a developer of project A might have 3
> separate checkouts:
>
> /Dev
> - /AppA (from AppA/trunk)
> - /LibA (from LibA/trunk)
> - /LibB (from LibB/trunk)
>
> With this directory layout, does this mean it is impossible to do an
> atomic commit that changes AppA and LibA at the same time? I noticed
> from /Dev I can do a svn mv between two working copies, but of course I
> cannot do a svn commit from /Dev, so the move cannot be atomic. Is there
> a way I can organize it better? It seems unreasonable to have people
> check out from a higher level as they will get the entire repository. Or
> is the solution in this case just to "deal with it" -- each project is
> conceptually separate so their commits will not be intermixed?
See this issue:
http://subversion.tigris.org/issues/show_bug.cgi?id=2381
It includes a link to a hacky workaround. Basically checkout an empty
folder somewhere and copy its .svn folder to /Dev. This gets by the
checking that SVN does to see if there is a common WC.
--
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