On Monday 19 Mar 2012 23:12:15 Steve Dougherty wrote: > I'm all for it. The coding standard is rather clear on indenting with > tabs, so I guess all that would be required is a run with a > re-indenting/code style conformance tool. That's something for a > janitor tree, and would ideally be timed between releases and when all > known pull requests have been merged or rejected to minimize > whitespace-related disruption to existing work.
Gigantic third party patches should come with some means to verify them. For example, converting all the spaces to tabs in a single commit is fine because then you can just do diff -uw. However, automated bulk indenting doesn't always makes things easier to read - e.g. devs may not like the style it produces. > > On 03/19/2012 06:13 PM, Marco Schulze wrote: > > May I add a vote to standardise indentation? This mess of spaces > > with tabs really bugs me. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20120320/c01b398d/attachment.pgp>
