Say I make some global networking API change, and this required
a significant edit to ipsec to make it comply with the new
structure layout or whatever.
And let's assume there is only one clear way to implement the
change, no other way to do the change would make any sense at all.
So the IPSEC people would have to effectively avoid integrating my
change, ie. it is a big onus on them to make their version of the API
update different enough from my edits so that nobody can claim they
just applied my change.
And the fact that there would be two edits makes no sense. If a
change has to occur twice in two different ways this makes merging a
So someone quips "just let them edit and just merge from IPSEC" and
I say I refuse to let something just sit in the tree that I cannot
edit when I want to make sweeping changes across the tree. That is
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/