diff options
author | 2010-04-06 16:16:59 -0700 | |
---|---|---|
committer | 2010-04-22 15:24:56 -0700 | |
commit | e234ebf7881c013b654113f0a208977ac3ce1d01 (patch) | |
tree | 0d34b2ef7502e051edd64f32327e6ca2d83c114b | |
parent | Documentation: -stable rules: upstream commit ID requirement reworded (diff) | |
download | linux-e234ebf7881c013b654113f0a208977ac3ce1d01.tar.gz linux-e234ebf7881c013b654113f0a208977ac3ce1d01.tar.bz2 linux-e234ebf7881c013b654113f0a208977ac3ce1d01.zip |
Documentation/HOWTO: update git home URL
Update git home page info.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-rw-r--r-- | Documentation/HOWTO | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/HOWTO b/Documentation/HOWTO index f5395af88a41..40ada93b820a 100644 --- a/Documentation/HOWTO +++ b/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 |