Re: [Libphidget-devel] make indent

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

On Sat, 2002-09-07 at 23:09, Vadim Tkachenko wrote:
> According to Jack Strohm:
> > On Sat, 2002-09-07 at 21:29, Vadim Tkachenko wrote:
> > > Hello,
> > > 
> > > I'm going to introduce two top-level targets:
> > > 
> > > make indent
> > > make indent-local
> > > 
> > > First one indents all the .c, .h and .cc files according to ./indent.rules
> > > file content (so the CVS stays consistent), and the second will indent all
> > > the files according to current user's $HOME/.indent.pro content.
> > > 
> > sounds good to me.    Have you worked with indent before?  I haven't.
> 
> Just a little bit, but reading the man page once, carefully, is enough.
> 
> This is what I'll do: I'll commit the things *related* to indent, however, I
> will not do 'make indent' before commiting the changes, so you have a chance
> to play around with $HOME/.indent.pro and see what kind of indentaion you
> like.
> 
> As for the project, I'd say just go with --gnu-style... Maybe with minor
> modifications.
> 
> Funny thing, though, indent breaks the very long return statements in the
> switch statement in phidget.c, so that has to be fixed manually - but just
> the first time...


how does this affect CVS.  

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 . . .