[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [openrisc] opencores comunity guidelines

To: openrisc@opencores.org
Subject: Re: [openrisc] opencores comunity guidelines
From: Richard Prescott <rip@step.polymtl.ca>
Date: Mon, 21 Apr 2003 13:11:10 -0400 (EDT)
In-Reply-To: <200304181532.56190.markom@opencores.org>
References: <200304181532.56190.markom@opencores.org>
Reply-To: openrisc@opencores.org
Sender: owner-openrisc@opencores.org

On Fri, 18 Apr 2003, Marko Mlinar wrote:

> *	When modifying existing code, formatting and white-spaces should be
> preserved.

For now it is fine but to prevent some mess I highly suggest enforcing a
coding standard and a coding style (including a .emacs and/or .vimrc.)
For the sake of simplicity, I propose to follow as-is the GNU or Linux
kernel one.

Richard

--------------------------------------------------------------------------
     1024D/BEF5DD36 Richard Prescott <rip@step.polymtl.ca>
     Key fingerprint = E11B E939 8A1D 2FA8 A672  555F ABA8 DE5A BEF5 DD36
--
To unsubscribe from openrisc mailing list please visit http://www.opencores.org/mailinglists.shtml

References:
- [openrisc] opencores comunity guidelines
  - From: Marko Mlinar <markom@opencores.org>

Prev by Date: [openrisc] First steps
Next by Date: Re: [openrisc] First steps
Prev by thread: [openrisc] opencores comunity guidelines
Next by thread: [openrisc] Re: [ECOS] OpenRISC eCos package
Index(es):
- Date
- Thread