[dev] NOTICE: Planned style conversion Monday, Jul 17

Quentin Young qlyoung at cumulusnetworks.com
Sat Jul 15 16:19:31 EDT 2017

I'm not sure I understand what the use case is here. At this point patch
volume against stable/3.0 and stable/2.0 is low enough that I think this is
really an edge case. In any case you can use the -w flag to diff which
should get you 90% of the way there.

On Fri, Jul 14, 2017 at 7:06 PM, Michael Richardson <mcr at sandelman.ca>

> Quentin Young <qlyoung at cumulusnetworks.com> wrote:
>     > This patch will not be submitted in a pull request. This will be a
>     > direct push to master. All stable branches will remain as-is. Code
>     > submissions against those branches -- which should by now be limited
> to
>     > bug fixes -- should continue to follow the style guide present in
> those
>     > branches.
> I think you should permit backported code, when it is an entire function,
> to remain in the new style so that it will be easier to verify that the
> code
> is the same as in master.
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20170715/1ad703a4/attachment.html>

More information about the dev mailing list