[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Advice on commit comments
From: |
Roddie |
Subject: |
Advice on commit comments |
Date: |
Sat, 15 Oct 2005 11:56:57 +0100 |
User-agent: |
Microsoft-Entourage/10.1.0.2006 |
I've been using CVS to manage website development for a couple of months,
and find that I am committing quite often.
I have a development sandbox on my Mac laptop and a live sandbox on my Linux
co-lo. I find I'm making smallish edits on the Mac and then needing to
commit them and update the co-lo to see the effect there. The co-lo files
are used among other things to see how the site looks on a PC. CVS makes
this so much easier than it used to be!
But I'm unsure of how much detail to put in the commit comments. Can anyone
advise on useful/common/best practice. For example, should I edit out the
CVS at the beginning of some of the lines so that the list of add/modified
files is not removed automatically? Are most commit comments just a few
words, or is it typical for some to be lengthy descriptions. Currently there
is only me using the repository, but I envisage a time when there will be
other users.
Thanks
Roddie Grant
- Advice on commit comments,
Roddie <=