From: Andrew Morton <akpm@linux-foundation.org>
To: linux-kernel@vger.kernel.org
Subject: avoiding rejects
Date: Tue, 10 Jul 2007 12:44:22 -0700 [thread overview]
Message-ID: <20070710124422.a52b0458.akpm@linux-foundation.org> (raw)
There are many situations where patching the kernel involves adding a new
item to a list, such as:
- adding a makefile line
- adding a new #include
- adding a new Kconfig entry
- adding a new PCI ID
- adding a record to feature-removal.txt
- adding a new sysctl table entry
- etc
Of course, everyone just sticks the new entry at the end of the existing
entries. This strategy carefully maximises the opportunity for patch
rejects and leads to unhappiness.
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.
next reply other threads:[~2007-07-10 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 19:44 Andrew Morton [this message]
2007-07-10 20:19 ` avoiding rejects Dan Aloni
2007-07-10 21:06 ` Geert Uytterhoeven
2007-07-10 22:03 ` Arnd Bergmann
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=20070710124422.a52b0458.akpm@linux-foundation.org \
--to=akpm@linux-foundation.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