[syslinux] Time to set a coding style for Syslinux?
Miller, Shao
Shao.Miller at yrdsb.edu.on.ca
Sun May 24 16:42:38 PDT 2009
So can we all of us commit to some sort of cut-over date, where we can
be very aware that any new code developed during the (hopefully very
quick) window might need to be adapted for after the cut-over? Maybe
best to not develop any new code during that window, but perhaps pitch
in effort for code clean-up during the window? Some things mentioned in
the link you gave including variable naming... If such are cleaned up,
or even files moved around and/or renamed, atomicity would be nice. :)
- Shao
-----Original Message-----
From: H. Peter Anvin [mailto:hpa at zytor.com]
Sent: Sunday, May 24, 2009 19:26
To: Miller, Shao
Cc: SYSLINUX Mailing list; liu Aleaxander;
claudiu.bogdan.mihail at gmail.com; Erwan Velu; Pierre-Alexander Meyer;
Gene Cumm; Sebastian Herbszt
Subject: Re: Time to set a coding style for Syslinux?
Miller, Shao wrote:
> I'd highly agree with four spaces versus eight! Will have to review
the
> coding style link you sent for the rest. Ironing out a consistent
style
> seems nice... For some of the formatting, I'm sure there're automated
> tools, but if you'd like to go insofar as renaming variables and
> functions to conform to a standard, I would gather that you'd like a
> hand tackling the workload for a cut-over. Happy to help, there. -
> Shao
I figure using an automatic tool for the cut-over, and then clean up
things afterwards. And yes, help would be appreciated.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
More information about the Syslinux
mailing list