avoiding rejects

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: avoiding rejects
    • From: Jan Engelhardt <[email protected]>
  • Re: avoiding rejects
    • From: Boaz Harrosh <[email protected]>
  • Re: avoiding rejects
    • From: Geert Uytterhoeven <[email protected]>
  • Re: avoiding rejects
    • From: Dan Aloni <[email protected]>

• Prev by Date: Re: [PATCH] include private data mappings in RLIMIT_DATA limit
• Next by Date: Re: [patch] mm: recheck lock rlim after f_op->mmap() method
• Previous by thread: [PATCH] mtd: Add sync/unblank function to mtdoops
• Next by thread: Re: avoiding rejects
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]