RE: Re: Revision log entry - making them mandatory

It isn’t the developer’s work which is being questioned, it is mine! They
are quite happy to make the changes, they just don’t/wont say why! Besides
which, one of the developers I work with said that “good developers are
expensive”! I think he was joking!

My reason for making the entries mandatory is that previous the working
environment has been VERY VERY flexible, to the point that for god knows how
long they have been developing and releasing code ON the live environment!
So it is really a time issue, and a changing habits issue.

But I have progressed. tsvn:logminsize is something which is “extracted”
from the repository with each check out or update, and will provide a
certain degree of control. However, my colleague was able to get round this
very quickly by changing the folder properties himself! I know that this
change would show up in the folder log, the same as any blank logs. I also
know that very few of the developers would take the time to repeatedly
change the property values. But until I am able to create build and apply
both a log template and a pre-commit hook, is there a way to prevent users
from changing the logminsize property?

Adam.

  _____

From: lassevk_at_gmail.com [mailto:lassevk_at_gmail.com] On Behalf Of Lasse
Vågsæther Karlsen
Sent: 23 January 2008 13:53
To: users_at_tortoisesvn.tigris.org
Subject: Re: Re: Revision log entry - making them mandatory

On Jan 23, 2008 2:52 PM, awoodjetts <adam.woodjetts_at_rentokil-initial.com>
wrote:

Many thanks to those who have assisted in my (re)direction of efforts and
searches. I believe that as I want to force the user to do this, I therefore
need to implement this on the server side not the client side. This mean
that unless I have missed something, I can't set the tsvn:logminsize
property as this requires modifications to each client (I sort of hope I am
wrong and someone can tell me how to set this property on the server).

Leaving me with the pre-commit hook. Based on the information provided by
Milen and that available after following the directions in the TSVN help, I
am in a position to experiment with this idea. However, Lubbe makes a very
good point, about the actual contents of the mandatory message. Does anyone
have any information about how to prevent spurious messages, without
resorting to a "disciplinary procedure"!

Yes, hire good programmers that take pride in their code instead of 9-5
people.

Thanks again.

Adam.

-----Original Message-----
From: Lübbe Onken | RA Consulting [mailto:l.onken_at_rac.de]
Sent: 23 January 2008 13:42
To: users_at_tortoisesvn.tigris.org
Subject: RE: Re: Revision log entry - making them mandatory

Hi Milen A. Radev,

You wrote:

> Like this one (I'm sure there are many other available "out there"):

Very friendly solution. It even tells the user indirectly that "aaaaaaaaaaa"
log message will be acceptable. A *real BOFH* pre-commit hook would run the
log messages through a spell-checker and reject all commits that don't pass
:D

Cheers
- Lübbe

--
      ___
 oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
  \ \_/_\_/>    The coolest Interface to (Sub)Version Control
  /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
--------------------------------------------------------------------- 
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org 
-- 
Lasse Vågsæther Karlsen
mailto:lasse_at_vkarlsen.no
http://presentationmode.blogspot.com/ 
PGP KeyID: 0xBCDEA2E3