not splitting up commits (was Re: [Phpwiki-talk] 1.3.3; and towards 1.4)

[Carsten K. <car...@ma...>]

Hi Steve,

I noticed Project Builder does split up cvs commits by directory, even if 
I only do one commit with files highlighted across multiple directories. 
Sometimes I do commit from the command-line, but for me doing multiple 
commits is quicker in the gui especially when there are other scattered 
modified files which are not ready to commit yet (or will never be 
committed).

Honestly I had been making the effort to intentionally split up commits 
when the comments are a little different for each of the files, so that 
inspection of cvs logs (hidden away as Get Info in Project Builder's 
Project menu) for individual files describe only the changes to that 
particular file.

So to reduce the number of commit emails I'm happy to use the shell more 
often when doing commits, and to avoid splitting up commits just for the 
sake of comments, unless say, it's very significant change to code and not 
just css or html template files.

Thanks for bringing this up.

:-) Carsten


On Thursday, February 21, 2002, at 10:40  am, Steve Wainstead wrote:

>
> Carsten, not to publicly flog you, but one of the reasons I've fallen 
> behind on the CVS list is because of the volume of checkins you make. (Oh 
> that all open source projects had such a complaint! :-) I have been 
> wondering: if you make the same change to 10 different files, do you 
> check in each one individually? It looked that way to me in the past. I 
> haven't tried coding PhpWiki in ProjectBuilder yet, and it wouldn't 
> suprise me if there were no way to do this (check in ten files at once). 
> We could teach you to check in from the Terminal app and possibly save 
> you a lot of work.
>
> cheers
> ~swain