Re: [Libphidget-devel] make indent

[Jack S. <js...@ja...>]

On Sun, 2002-09-08 at 03:16, Vadim Tkachenko wrote:
> According to Jack Strohm:
> 
> > if I check something out, then run make indent-local, edit a few
> > things.  How do I check the code back in.
> > 
> > make indent
> > cvs commit
> > 
> > if so, does that mean CVS will check every file into version control,
> > because they all have changes (at least the data on the file has).
> > 
> > Just wondering . . .
> 
> The proper sequence is like this:
> 
> cvs get/update
> make indent-local
> hack away
> make indent
> cvs commit

ok.

> 
> There'll be one massive commit because all the code has to be brought to
> compliance, and then the diffs will become civilized. The only thing is to
> just remember to do 'make indent' before 'cvs commit' ;) Along the Ant
> lines, it may be a good idea to create 'make commit', though the usefulness
> will be limited due to the fact that you may want to commit one file.
> Another solution is to integrate the indentation with CVS, though I don't
> remember how to do it and have to read the SourceForge docs again.
> 
> Did 'make indent' break things on your boxes? I'm still wondering *why* does
> it break the return statements the first time, but not subsequent...

everything seemed to work for me.

> 
> Another thing - I might make 'make indent' slower, but smarter - right now,
> if I do it twice in a row, even though the files are identical, the
> timestamp changes, and it'll recompile all the project. It's relatively easy
> to avoid it.

yeah

> 
> So it works for you, right? Time to 'make indent && cvs commit'?

yep!