[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Mixing recursive and non-recursive commits

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Fri, 02 Aug 2013 18:05:19 +0100

"Braun, Eric" <eric.braun_at_medtronic.com> writes:

> I don't know why this is
> should be complicated to do from the command line when GUI clients are
> already doing this today. I would use a GUI client to do this work in
> most cases but GUI's don't work as well when defining
> wildcards/filtering (*/*/file for example for a commit target).

It probably would not be that complicated to implement something,
although the code in question is already quite complex. One problem is
determining exactly what to implement in the corner cases. The bigger
obstacle is determining whether this feature will be useful. How many
people are going to use it? I have never made a commit where this
behaviour would have been helpful but other people use Subversion

One corner case: suppose I have a directory A/ in the working copy and
repository. I add directory B/, files A/f and B/f and set properties
associated with the new files on A/ and B/. Now a commit --with-parents
of A/f and B/f includes B/, because it is added, and that includes the
property changes on B/. Do the property changes on A/ get included in
the commit or not? Will we need another option to give the other

Another corner case: how does it interact with --changelist? The commit
is limited to targets in the changelist so I suppose --with-parents
would only apply to those items?

Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
Received on 2013-08-02 19:06:00 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.