So far, the consensus seem to be: - Devel list is not desirable at this time. I will continue to post major announcements to syslinux-announce, of course. - The 4-space coding standard seems to get most favor. I would like to run reformatting jobs immediately after the 3.81 release; the expectation is that other people will run the same reformatting on any code merged after that point (roughly by the end of the week.) OK with everyone? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
H. Peter Anvin wrote:> So far, the consensus seem to be: > > - Devel list is not desirable at this time. > > - The 4-space coding standard seems to get most favor.I'm going to so OK... As Ryan McLean said, hearing about bugs and stuff is actually helpful. And new feature discussion, etc... I can't think of how many times I've found out about bug fixes and new features by simply listening in on the list. TB ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. **********************************************************************
Luciano Miguel Ferreira Rocha
2009-May-26 09:28 UTC
[syslinux] Devel list, coding standards
On Mon, May 25, 2009 at 09:49:00PM -0700, H. Peter Anvin wrote:> So far, the consensus seem to be: > > - Devel list is not desirable at this time. > I will continue to post major announcements to syslinux-announce, of > course. > > - The 4-space coding standard seems to get most favor. I would like to > run reformatting jobs immediately after the 3.81 release; the > expectation is that other people will run the same reformatting on any > code merged after that point (roughly by the end of the week.)Well, is it 4 spaces, or 4 spaces, 1 tab, 1 tab + 4 spaces? Or is it 1 tab that gets displayed as 4 spaces? Modelines for vim and/or emacs would be appreciated. Regards, Luciano Rocha -- lfr 0/0
Fine by me... Will the tools used to auto-format be named in the git commit for the cut-over? A pre-commit task could then be to run such tools to ensure consistency. - Shao -----Original Message----- From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of H. Peter Anvin Sent: Tuesday, May 26, 2009 00:49 To: SYSLINUX Mailing list Subject: [syslinux] Devel list, coding standards So far, the consensus seem to be: - Devel list is not desirable at this time. I will continue to post major announcements to syslinux-announce, of course. - The 4-space coding standard seems to get most favor. I would like to run reformatting jobs immediately after the 3.81 release; the expectation is that other people will run the same reformatting on any code merged after that point (roughly by the end of the week.) OK with everyone? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. _______________________________________________ Syslinux mailing list Submissions to Syslinux at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
Miller, Shao wrote:> Fine by me... Will the tools used to auto-format be named in the git > commit for the cut-over? A pre-commit task could then be to run such > tools to ensure consistency. - ShaoI have already checked in the "Nindent" script I will use for the first pass. -hpa