Re: Mixing recursive and non-recursive commits
"Braun, Eric" <eric.braun_at_medtronic.com> writes:
> If do a google search for "svn commit parents" you'll see I'm not the
> first to unofficially request this and come across this issue. I
> suspect most others just kludged around this and found a subtree to
> checkin with additional work involved. I see the need for this quite
> often when I'm running scripts that interactive with multiple
> directory trees. Quite often the scripts create new dirs with new
> files that I want to checkin. So I add these with --parents. When
> completed though I may want to selectively checkin certain files w/ a
> given comment (not the whole subtree).
> Regarding your corner cases if we stick to the explanation that only
> newly added parent directories (and their properties set) will get
> added to the commit list then this handles these scenarios. In the
> first scenario the property updates in A would NOT be committed
> because A is not a newly added parent directory. In the second corner
> case items in the changelist plus any newly added parent directories
> is what would be committed.
The problem I have is that the simple behaviour leads to inconsistencies
such as modified parents with properties. You suggest resolving that
inconsistency in a particular way but as far as I can see other
behaviours are just as reasonable. You describe the feature as "added
parents" but somebody else could describe it as "automatic parents" and
want the other behaviour. If we implement one behaviour now how do we
extend it in the future?
I don't see many requests for this behaviour and in this thread the
discussion is mostly you and me. To make progress we need consensus on
the desired behaviour and that is hard when there are so few voices.
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Received on 2013-08-20 16:40:14 CEST
This is an archived mail posted to the Subversion Users