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

Re: [Locking] commit and unlock

From: Folker Schamel <schamel23_at_spinor.com>
Date: 2004-12-17 09:37:22 CET

>> c) first_file.txt and second_file.txt have been shown on the
>> modified file list, and both of them have been unlocked after
>> the commit (even when content of second_file.txt was unmodified).
> This is pernicious, and it is Microsoftesque: The program is telling me
> it knows better than I do what I intend. If I locked a file and didn't
> work on it, it means I still want it locked.

But if you only worked on first_file.txt, you should have been
trained to only svn commit foo/first_file.txt, don't you agree? ;-)

When using svn commit foo/, you are explicitely telling svn
that you've done your work on the complete directory foo/.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 17 09:38:32 2004

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

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