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

Re: [Issue 533] New - implement reserved checkouts

From: <brane_at_xbc.nu>
Date: 2002-08-06 22:40:06 CEST

Karl Fogel wrote:

>brane@xbc.nu writes:
>
>
>>At the risk of being boring, I'll (again) describe how ClearCase
>>does this: It asks for a commit log message at _checkout_ time,
>>i.e., when you lock a file or directory. That message is visible to
>>other users, and serves as the template for the "real" log message
>>at commit time.
>>
>>
>
>A thought:
>
>A nice thing about this (and about Greg's solution -- the two seem
>pretty similar) is the opportunity to provide extra information at the
>time you take out the lock, and use that information at commit time.
>
>Are you thinking what I'm thinking? Issue numbers, baby! :-)
>
:-)

>So others could see not just
>
> "Jane is working on foo.c and bar.c"
>
>but even:
>
> "Jane is working on foo.c and bar.c, to resolve issue #blah"
>
>There might be a tight relationship between lock communications and
>log message templates here. Does that match your experience with
>Clearcase?
>
>

It all depends on how disciplined users are. Because ClearCase doesn't
_force_ you to write a log message in advance, and lets you modify it on
commit, it's possible to have totally misleading log msg templates. I've
seen that happen. But most of the time, those templates are very useful.

One nice feature is that you (the lock owner) can modify the log message
template without committing; say, if you find that you weren't quite
prescient enough about how to fix a bug.

-- 
Brane ─îibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 6 22:40:40 2002

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.