[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [RFC] CodingStyle
From:       Rob Landley <rob () landley ! net>
Date:       2006-02-24 16:33:12
Message-ID: 200602241133.12569.rob () landley ! net
[Download RAW message or body]

On Friday 24 February 2006 1:06 am, David Seikel wrote:
> On Thu, 23 Feb 2006 21:48:26 +0000 Andy Green <andy@warmcat.com> wrote:
> > Mike Frysinger wrote:
> > > On Thursday 23 February 2006 14:33, Andy Green wrote:
> > >> each new rule makes it harder for people to contribute.
> > >
> > > if you've ever looked at some of the stuff that's been merged,
> > > you'll see that rarely do we reject code because of its style
> >
> > Sounds good then.
> >
> > I was just looking at GNU indent, if push comes to shove one could run
> > it on the whole tree on checkout, then diff out the edits and patch
> > them back into the un-indented source.
>
> If you have a style guide, you really need a matching indent.pro or
> equivalent.  It's not so important to automate it's use, it's only
> important that there is one and it's in cvs.  A style guide without a
> matching indent.pro is just a rant.

You'd prefer I remove the style guide?

> Oh, and not everybody uses vi and/or emacs, so stuff to support those is
> not generally useful.

It's useful to me, and when Erik used emacs it was useful to him.  That's good 
enough for me.

Rob
-- 
Never bet against the cheap plastic solution.
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]