From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Simon Horman <horms@verge.net.au>
Cc: Cong Wang <xiyou.wangcong@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: kdump.txt new web address for kexec-tools on kernel.org after the hacking
Date: Mon, 21 Nov 2011 07:41:23 -0800 [thread overview]
Message-ID: <4ECA7123.8020006@gmail.com> (raw)
In-Reply-To: <20111121052858.GE11378@verge.net.au>
On 11/20/2011 09:28 PM, Simon Horman wrote:
> On Sun, Nov 20, 2011 at 05:49:26PM +0800, Cong Wang wrote:
>> On Sun, Nov 20, 2011 at 2:23 PM, Justin P. Mattock
>> <justinmattock@gmail.com> wrote:
>>> seems kexec-tools has been moved somewhere else than any of the addresses on
>>> kdump.txt
>>>
>>> is there a new location? is the author know about this? I can supply a patch
>>> I just need some _legit_ addresses to use; google is giving me some, but im
>>> not sure what they are/or should I use them
>>
>> The git tree has been moved to,
>> git://github.com/horms/kexec-tools.git
>>
>> Simon, any plan to move back to kernel.org?
>
> Yes. I plan to attend the Automotive Linux Summit in Yokohama next monday
> and have my key signed at that event. After that I intend to re-establish
> my access to kernel.org and move the kexec-tools tree back to kernel.org.
>
cool! so next week after the key signing, and kernel.org adds
kexec-tools back in.. then there is no need for a patch _if_ the
addresses are not changed, but if they are then I would imagine the
author has that taken care of then.
Justin P. Mattock
next prev parent reply other threads:[~2011-11-21 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 6:23 kdump.txt new web address for kexec-tools on kernel.org after the hacking Justin P. Mattock
2011-11-20 9:49 ` Cong Wang
2011-11-21 5:28 ` Simon Horman
2011-11-21 15:41 ` Justin P. Mattock [this message]
2011-11-22 0:28 ` 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=4ECA7123.8020006@gmail.com \
--to=justinmattock@gmail.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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