You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Dave Rodgman <da...@arm.com> on 2005/08/15 12:40:51 UTC
should I raise an issue? commit multiple dirs without parent WC
Hi,
as previously discussed, the subversion commandline client won't commit
multiple directories [from a single repository], unless they have a
parent directory which is a working copy. Under the right circumstances,
it seems to work if the parent is any arbitrary directory, but arranging
the working copy this way starts becoming awkward.
Given that a common subversion repository layout (at least round here)
is:
module1/trunk/...
module/branch/...
people often checkout module1/trunk as module1; given that people
usually want to work with a set of modules from a single branch, this
seems like a reasonable thing to do. For projects imported from CVS,
this is necessary from a build point of view, since this is the same
structure created by CVS - this is a big issue for us.
Anyway, the upshot is that people often want to do
svn ci module1 module2
but can't.
Should I raise an issue about this? I couldn't find one in the issue
tracker. It might seem trivial but in some ways seems to undermine the
very nice "atomic commits" property that subversion provides.
Previous discussion at:
http://svn.haxx.se/users/archive-2005-02/1070.shtml
http://www.chiark.greenend.org.uk/~sgtatham/svn.html (section 7.4,
discusses work-around)
Regards,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: should I raise an issue? commit multiple dirs without parent
WC
Posted by Dave Rodgman <da...@arm.com>.
On Mon, 2005-08-15 at 22:34 +0100, Max Bowsher wrote:
> Dave Rodgman wrote:
> > Hi,
> >
> > as previously discussed, the subversion commandline client won't commit
> > multiple directories [from a single repository], unless they have a
> > parent directory which is a working copy. Under the right circumstances,
> > it seems to work if the parent is any arbitrary directory, but arranging
> > the working copy this way starts becoming awkward.
> I think this is a valid, though minor, bug. I thought we had an issue
> already, but I just looked through the entire list and couldn't find it, so
> yes, please go ahead and file an issue.
Raised as issue 2381
regards,
Dave
>
> Max.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: should I raise an issue? commit multiple dirs without parent WC
Posted by Max Bowsher <ma...@ukf.net>.
Dave Rodgman wrote:
> Hi,
>
> as previously discussed, the subversion commandline client won't commit
> multiple directories [from a single repository], unless they have a
> parent directory which is a working copy. Under the right circumstances,
> it seems to work if the parent is any arbitrary directory, but arranging
> the working copy this way starts becoming awkward.
>
> Given that a common subversion repository layout (at least round here)
> is:
>
> module1/trunk/...
> module/branch/...
>
> people often checkout module1/trunk as module1; given that people
> usually want to work with a set of modules from a single branch, this
> seems like a reasonable thing to do. For projects imported from CVS,
> this is necessary from a build point of view, since this is the same
> structure created by CVS - this is a big issue for us.
>
> Anyway, the upshot is that people often want to do
>
> svn ci module1 module2
>
> but can't.
>
> Should I raise an issue about this? I couldn't find one in the issue
> tracker. It might seem trivial but in some ways seems to undermine the
> very nice "atomic commits" property that subversion provides.
>
> Previous discussion at:
>
> http://svn.haxx.se/users/archive-2005-02/1070.shtml
> http://www.chiark.greenend.org.uk/~sgtatham/svn.html (section 7.4,
> discusses work-around)
I think this is a valid, though minor, bug. I thought we had an issue
already, but I just looked through the entire list and couldn't find it, so
yes, please go ahead and file an issue.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org