×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Mark S. Waterbury
As you can see, svn makes it rather easy for anyone to "break the lock"
I read that just a couple days ago. Anyone can break a Subversion lock. That's one more point in favor of implementing one's own locking mechanism against IBM i source members, as an option. At least, that would be one way of blocking other's changes to a source member in the library file system, if that's what a programmer intends.
Of course, that wouldn't prevent anyone from getting a copy of the member from the Subversion repository, and committing changes to it, in the mean time. In that case, it would put the onus on the IBM i Subversion client to not forward those changes (copy) to the library-file-member; but rather to honor the lock.
-Nathan.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
