From: Borislav Petkov <bp@alien8.de>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: Leonard Tse <xiehao5@gmail.com>,
ftpadmin@kernel.org, linux-kernel@vger.kernel.org,
greg@kroah.com, leoli@freescale.com, triplex@zh-kernel.org,
tshibata@ab.jp.nec.com, k-keiichi@bx.jp.nec.com,
minchan.kim@gmail.com
Subject: Re: [PATCH]URL is unavailable
Date: Thu, 13 Sep 2012 11:32:42 +0200 [thread overview]
Message-ID: <20120913093241.GA15810@liondog.tnic> (raw)
In-Reply-To: <5051334E.4010802@kernel.org>
On Wed, Sep 12, 2012 at 09:13:50PM -0400, Konstantin Ryabitsev wrote:
> On 12/09/12 12:03 PM, Borislav Petkov wrote:
> > Dear KORG admins, what are the chances of userweb.kernel.org coming back
> > online?
>
> Hello:
>
> There is no ETA on that service being available. It may not ever come
> back, at least not in the way it was before.
>
> That being said, I'm perfectly willing to set up a few redirects in
> place if broken URLs are causing problems. I just cannot use any of the
> existing backups of userweb data, as it is under a strict "do not use,
> ever" quarantine.
>
> If someone can provide me with trusted backups of that data, I will
> provide hosting and redirects to unbreak the URLs.
My memory is hazy on this, but after the move, what's the policy on
enabling users.kernel.org or userweb.kernel org or some other user web
serving thing? I vaguely remember that we don't want to do this anymore
but I'm not sure.
In any case, if we do, it would probably be better to have a whole
different machine for such stuff and let users upload their stuff again
without touching the old backups at all...
Hmm.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-09-13 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 15:51 Leonard Tse
2012-09-12 16:03 ` Borislav Petkov
2012-09-12 22:35 ` Leonard Tse
2012-09-13 1:13 ` Konstantin Ryabitsev
2012-09-13 9:32 ` Borislav Petkov [this message]
2012-09-13 13:35 ` Konstantin Ryabitsev
2012-09-13 13:55 ` Borislav Petkov
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=20120913093241.GA15810@liondog.tnic \
--to=bp@alien8.de \
--cc=ftpadmin@kernel.org \
--cc=greg@kroah.com \
--cc=k-keiichi@bx.jp.nec.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan.kim@gmail.com \
--cc=mricon@kernel.org \
--cc=triplex@zh-kernel.org \
--cc=tshibata@ab.jp.nec.com \
--cc=xiehao5@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
all inboxes | Powered by JetHome®