From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: avoiding rejects
Date: Wed, 11 Jul 2007 00:03:48 +0200 [thread overview]
Message-ID: <200707110003.49287.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707102306030.10340@anakin>
On Tuesday 10 July 2007, Geert Uytterhoeven wrote:
>
> > Most of these lists are unordered anyway, so inserting the new item at a
> > randomly-chosen position is a better approach than just appending it.
>
> Really?
>
> #includes should be sorted alphabetically
> Lots of other stuff should be sorted numerically/alphabetically
>
I would also argue that adding in an ordered way is better than
at random positions, that is if the list is ordered to start with.
As long as everyone follows the same order, you will get (desired)
conflicts in case two people try to add the same line, and when
the added lines are different, it's as good as random ordering
to avoid undesired merge conflicts.
Arnd <><
next prev parent reply other threads:[~2007-07-10 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 19:44 avoiding rejects Andrew Morton
2007-07-10 20:19 ` Dan Aloni
2007-07-10 21:06 ` Geert Uytterhoeven
2007-07-10 22:03 ` Arnd Bergmann [this message]
2007-07-11 8:21 ` Boaz Harrosh
2007-07-11 9:44 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707110003.49287.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox