summaryrefslogtreecommitdiff
path: root/2008/how_and_why_kernel-fht2008/html/mgp00033.txt
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2015-10-25 21:00:20 +0100
committerHarald Welte <laforge@gnumonks.org>2015-10-25 21:00:20 +0100
commitfca59bea770346cf1c1f9b0e00cb48a61b44a8f3 (patch)
treea2011270df48d3501892ac1a56015c8be57e8a7d /2008/how_and_why_kernel-fht2008/html/mgp00033.txt
import of old now defunct presentation slides svn repo
Diffstat (limited to '2008/how_and_why_kernel-fht2008/html/mgp00033.txt')
-rw-r--r--2008/how_and_why_kernel-fht2008/html/mgp00033.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/2008/how_and_why_kernel-fht2008/html/mgp00033.txt b/2008/how_and_why_kernel-fht2008/html/mgp00033.txt
new file mode 100644
index 0000000..1ade7eb
--- /dev/null
+++ b/2008/how_and_why_kernel-fht2008/html/mgp00033.txt
@@ -0,0 +1,13 @@
+How and why to work with the Linux kernel community
+Practical Rules
+
+3. Merge your code upstream
+Initially you basically have to create a fork
+Development of upsteram project continues sometimes at high speed
+If you keep it out of tree for too long time, conflicts arise
+Submissions might get rejected in the first round
+Cleanups needed, in coordination with upstream project
+Code will eventually get merged
+No further maintainance needed for synchronization between your contribution and the ongoing upstream development
+Don't be surprised if your code won't be accepted if you didn't discuss it with maintainers upfront and they don't like your implementation
+
personal git repositories of Harald Welte. Your mileage may vary