aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes CVS Question: 2 Parts Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "CVS Question: 2 Parts" Watch "CVS Question: 2 Parts" New topic
Author

CVS Question: 2 Parts

Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15299
    
    6

The other day I setup a CVS server for myself at work. It can only be accessed when I am at work. So tonight I am working on some code, making some changes, adding some files etc. When I get to work tomorrow I am going to check in all my changes and additions.

I know using CVS you are supposed to comment on commits and I usually just type something quick like "added method for doing bla". But with as many changes as I am making what is the best way to keep track so that my commit comments are so long they make no sense.

Part 2 of this is, throughout the day, how often should I commit changes? Is there a standard so many lines of code, so many minutes/hours, etc? Is it completely up to me? I realize this might be different for me than from the norm as I have no one else working on the code so I don't have to worry about diffs.


GenRocket - Experts at Building Test Data
Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24184
    
  34

I find that on only-me projects, my commit messages aren't very useful and often don't make sense. But on group projects, where we have CVS mail check-in messages to everybody, I find I write them as if I'm sending an email to everybody telling them what I've done, and they're way better. You could try thinking of it that way, but personally, I've never been able to do a good job of writing CVS commit messages on one-man projects, either.

As far as how often: every time you get a green bar, and certainly no less than every half-hour or so. I follow this procedure both by myself and on group projects, where it's even more important.


[Jess in Action][AskingGoodQuestions]
Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15299
    
    6

Thanks Ernest. That helps.
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by Ernest Friedman-Hill:
But on group projects, where we have CVS mail check-in messages to everybody, I find I write them as if I'm sending an email to everybody telling them what I've done, and they're way better.


I feel similarly since Eclipse 3 supports commit sets (basically it groups incoming changes by commit comment in the synchronize view).


As far as how often: every time you get a green bar, and certainly no less than every half-hour or so. I follow this procedure both by myself and on group projects, where it's even more important.


Another take on it is to ask yourself: "If I do something really stupid now, would I be comfortable loosing all the work since the last checkin?" When the answer is "no", it's time for a commit...


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: CVS Question: 2 Parts