[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 3602]  Release locks of all commit targets, regardless of
From:       "C. Michael Pilato" <cmpilato () collab ! net>
Date:       2010-03-22 14:50:40
Message-ID: 20100322145040.A8CF9FCC0B0 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=3602






------- Additional comments from cmpilato@tigris.org Mon Mar 22 07:50:39 -0700 2010 -------
I've heard request for so-called "zero-change commits", too.  I've just not been
privy to the (undoubtedly valid) reasons for them.

But I want to keep *this* issue on track here, focusing on one thing.  At the
moment, I believe we're looking at "Why is it that only the changed files that
were targets of a commit get unlocked?" with the recommendation that *all*
locked files that were targets of a commit operation -- regardless of whether
they had changes, and regardless of whether a commit was attempted -- get
unlocked at the end of the attempted operation.

If we're actually talking about supporting zero-change commits (which perhaps
implies the behavior above), that's fine -- but let's make that clear in the
issue summary and future comments.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2463242

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]