This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Alexander Chemeris alexander.chemeris at gmail.comI completely support extension of the line with. 80 characters limit is very annoying these days. 120 is a good number. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CTO/Founder Fairwaves, Inc. https://fairwaves.co On Apr 1, 2017 12:45, "Harald Welte" <laforge at gnumonks.org> wrote: > Dear all, > > [Despite today being April 1st, this is not an april fool's joke] > > ever since the start of the Osmocom project, we have adopted pretty much > 1:1 the Linux Kernel coding style. > > Having a uniform coding style all over the project is important for > readability, and from my point of view it doesn't really matter too much > which style it is, as long as it is uniform accross the projects. > > I'm still fine with the Linux kernel coding style for most parts, but I > think we could consider allowing longer lines. 80 characters is still > nice here and there, but maybe something like 100, 120 or even 130 might > actually make the code more readable and permit us to use slightly > longer identifiers without having to wrap every second statement in the > code. > > What do people generally think here? > > Regards, > Harald > > -- > - Harald Welte <laforge at gnumonks.org> > http://laforge.gnumonks.org/ > ============================================================ > ================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170401/305b3c17/attachment.htm>