[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B74A4@saturn3.aculab.com>
Date: Wed, 18 Dec 2013 11:07:34 -0000
From: "David Laight" <David.Laight@...LAB.COM>
To: "Geert Uytterhoeven" <geert@...ux-m68k.org>,
"Peter Zijlstra" <peterz@...radead.org>
Cc: "David Miller" <davem@...emloft.net>,
"Stephen Rothwell" <sfr@...b.auug.org.au>,
<netdev@...r.kernel.org>,
"Linux-Next" <linux-next@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <ffusco@...hat.com>,
<dborkman@...hat.com>, <tgraf@...hat.com>,
"Joe Perches" <joe@...ches.com>
Subject: RE: linux-next: build failure after merge of the net-next tree
> > And sort(1) is annoying in that it doesn't do in-place sort; you'll end
> > up with empty files if you try the naive thing.
> >
> > Worse most of those Kbuild files include other random garbage, which
> > makes automated sorting harder still.
> >
> > So unless there's a sane and easy way to keep it sorted; I'm going to
> > ignore that rule.
>
> Not keeping them sorted causes merge conflicts and duplicate/missing
> entries.
Edit in vi put cursor on the first line to be sorted and type !}sort
(assuming there is a nice blank line at the end).
David
Powered by blists - more mailing lists