From 44f27025ae16b3ba43ac1a31642554842794ac89 Mon Sep 17 00:00:00 2001 From: Randy Dunlap Date: Tue, 6 Apr 2010 16:16:59 -0700 Subject: [PATCH] --- yaml --- r: 190153 b: refs/heads/master c: e234ebf7881c013b654113f0a208977ac3ce1d01 h: refs/heads/master i: 190151: c408b2d6c52dc9f1fc17e21e1302ecd3ab9e2ca8 v: v3 --- [refs] | 2 +- trunk/Documentation/HOWTO | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 10247fb5d7fa..5067e006b651 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 959fb1c5075c2dcdbe879e6dafbc59eb1e1192d6 +refs/heads/master: e234ebf7881c013b654113f0a208977ac3ce1d01 diff --git a/trunk/Documentation/HOWTO b/trunk/Documentation/HOWTO index f5395af88a41..40ada93b820a 100644 --- a/trunk/Documentation/HOWTO +++ b/trunk/Documentation/HOWTO @@ -234,7 +234,7 @@ process is as follows: Linus, usually the patches that have already been included in the -next kernel for a few weeks. The preferred way to submit big changes is using git (the kernel's source management tool, more information - can be found at http://git.or.cz/) but plain patches are also just + can be found at http://git-scm.com/) but plain patches are also just fine. - After two weeks a -rc1 kernel is released it is now possible to push only patches that do not include new features that could affect the