From c8fde753667793f6b0c18b46b345ae842ce66ed3 Mon Sep 17 00:00:00 2001 From: Juan Lang Date: Tue, 24 Jul 2007 13:24:19 -0700 Subject: [PATCH] --- yaml --- r: 63217 b: refs/heads/master c: a2765e81d8a58f66e21176ca2a8fd6012b187994 h: refs/heads/master i: 63215: 6bc09d66bee7fb6cb30e1c00c79ef864152a9a53 v: v3 --- [refs] | 2 +- trunk/Documentation/stable_api_nonsense.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 69c239454fbc..0515c9509b13 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 30b1b28001fef09ea31b1c87e8e8acb962d109e2 +refs/heads/master: a2765e81d8a58f66e21176ca2a8fd6012b187994 diff --git a/trunk/Documentation/stable_api_nonsense.txt b/trunk/Documentation/stable_api_nonsense.txt index a2afca3b2bab..847b342b7b20 100644 --- a/trunk/Documentation/stable_api_nonsense.txt +++ b/trunk/Documentation/stable_api_nonsense.txt @@ -10,7 +10,7 @@ kernel to userspace interfaces. The kernel to userspace interface is the one that application programs use, the syscall interface. That interface is _very_ stable over time, and will not break. I have old programs that were built on a pre 0.9something kernel that still work -just fine on the latest 2.6 kernel release. This interface is the one +just fine on the latest 2.6 kernel release. That interface is the one that users and application programmers can count on being stable.