Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Simon Horman <horms@verge.net.au>
Cc: Haren Myneni <hbabu@us.ibm.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdump: Update kdump documentation as kexec-tools-resting has been renamed kexec-tools
Date: Mon, 21 Jul 2008 08:37:06 -0400	[thread overview]
Message-ID: <20080721123706.GA4451@redhat.com> (raw)
In-Reply-To: <20080719011612.GA20745@verge.net.au>

On Sat, Jul 19, 2008 at 11:16:14AM +1000, Simon Horman wrote:
> Signed-off-by: Simon Horman <horms@verge.net.au>
> 
> --- 
> Reposting to Vivek's new email address
> 
> Index: linux-2.6/Documentation/kdump/kdump.txt
> ===================================================================
> --- linux-2.6.orig/Documentation/kdump/kdump.txt	2008-07-19 10:27:50.000000000 +1000
> +++ linux-2.6/Documentation/kdump/kdump.txt	2008-07-19 10:51:57.000000000 +1000
> @@ -65,26 +65,26 @@ Install kexec-tools
>  
>  2) Download the kexec-tools user-space package from the following URL:
>  
> -http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/kexec-tools-testing.tar.gz
> +http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/kexec-tools.tar.gz
>  
> -This is a symlink to the latest version, which at the time of writing is
> -20061214, the only release of kexec-tools-testing so far. As other versions
> -are released, the older ones will remain available at
> -http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/
> +This is a symlink to the latest version.
>  
> -Note: Latest kexec-tools-testing git tree is available at
> +The latest kexec-tools git tree is available at:
>  
> -git://git.kernel.org/pub/scm/linux/kernel/git/horms/kexec-tools-testing.git
> +git://git.kernel.org/pub/scm/linux/kernel/git/horms/kexec-tools.git
>  or
> -http://www.kernel.org/git/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=summary
> +http://www.kernel.org/git/?p=linux/kernel/git/horms/kexec-tools.git
> +
> +More information about kexec-tools can be found at
> +http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/README.html
>  
>  3) Unpack the tarball with the tar command, as follows:
>  
> -   tar xvpzf kexec-tools-testing.tar.gz
> +   tar xvpzf kexec-tools.tar.gz
>  
>  4) Change to the kexec-tools directory, as follows:
>  
> -   cd kexec-tools-testing-VERSION
> +   cd kexec-tools-VERSION
>  
>  5) Configure the package, as follows:

Looks Good. Thanks Simon.

Acked-by: Vivek Goyal <vgoyal@redhat.com>

Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-07-21 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19  0:58 [PATCH] kdump: Update kdump documentation as kexec-tools-resting has been renamed kexec-tools Simon Horman
2008-07-19  1:16 ` Simon Horman
2008-07-21 12:37   ` Vivek Goyal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-28  2:13 Simon Horman
2008-07-28  2:29 ` [PATCH] " Simon Horman

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=20080721123706.GA4451@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=hbabu@us.ibm.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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