From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: [PATCH 2/3] Documentation/HOWTO: update git home URL
Date: Thu, 22 Apr 2010 15:40:15 -0700 [thread overview]
Message-ID: <1271976016-3584-2-git-send-email-gregkh@suse.de> (raw)
In-Reply-To: <20100422222928.GA3268@kroah.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
Update git home page info.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
Documentation/HOWTO | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
index f5395af..40ada93 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
--
1.7.0.4
next prev parent reply other threads:[~2010-04-22 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 22:29 [GIT PATCH] driver core fixes for 2.6.34-git Greg KH
2010-04-22 22:40 ` [PATCH 1/3] Documentation: -stable rules: upstream commit ID requirement reworded Greg Kroah-Hartman
2010-04-24 2:02 ` tytso
2010-04-24 9:12 ` Stefan Richter
2010-04-24 9:30 ` Stefan Richter
2010-04-24 15:02 ` Greg KH
2010-04-24 16:50 ` Theodore Tso
2010-04-22 22:40 ` Greg Kroah-Hartman [this message]
2010-04-22 22:40 ` [PATCH 3/3] sysfs: use sysfs_attr_init in ASUS atk0110 driver Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1271976016-3584-2-git-send-email-gregkh@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox