From: "J.H." <warthog19@eaglescrag.net>
To: users@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
support@osuosl.org, Jon Tollefson <kniht@linux.vnet.ibm.com>,
Martin Bligh <mbligh@mbligh.org>,
"Jorge O. Castro" <jorge@ubuntu.com>,
bugme-admin@linux-foundation.org,
"FTPAdmin Kernel.org" <ftpadmin@kernel.org>
Cc: Jim Zemlin <jzemlin@linux-foundation.org>
Subject: [KORG] Bugzilla Upgrade / Server move
Date: Wed, 25 Mar 2009 00:13:33 -0700 [thread overview]
Message-ID: <49C9D99D.2050400@eaglescrag.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Evening Everyone,
Just a quick heads up to everyone http://bugzilla.kernel.org was taken
down for about an hour this evening to perform an upgrade that was
precipitated by a possible security vulnerability that we wanted to
squash quickly and avoid it going forward.
The code base has had a rather extensive upgrade, migrating custom
fields over to Bugzilla's 3.x custom field support, and dealing with
kernel.org specific changes.
Along with this upgrade http://bugzilla.kernel.org has moved onto the
kernel.org dynamic hosting machine, joining patchwork and our wikis on
this dedicated piece of hardware.
If you have any issues, problems, concerns, please don't hesitate to get
a hold of me, ftpadmin@kernel.org and/or bugme-admin@linux-foundation.org
- - John 'Warthog9' Hawley
Chief Kernel.org Administrator
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAknJ2Z0ACgkQ/E3kyWU9didIjQCfcIkjMhbc1TvqlMPAjgwDFk8p
orEAnAtJWGMfZJNuawlxSuRTBDbcGFcD
=0IE9
-----END PGP SIGNATURE-----
next reply other threads:[~2009-03-25 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 7:13 J.H. [this message]
2009-03-25 11:57 ` Alan Cox
2009-03-25 14:38 ` Martin Bligh
2009-03-25 20:21 ` [kernel.org users] " Pierre Ossman
2009-03-26 1:12 ` Dave Airlie
2009-03-26 7:11 ` Pierre Ossman
2009-03-26 7:23 ` Tejun Heo
2009-03-26 7:48 ` Stefan Richter
2009-03-26 8:04 ` Stefan Richter
2009-03-26 19:21 ` J.H.
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=49C9D99D.2050400@eaglescrag.net \
--to=warthog19@eaglescrag.net \
--cc=bugme-admin@linux-foundation.org \
--cc=ftpadmin@kernel.org \
--cc=jorge@ubuntu.com \
--cc=jzemlin@linux-foundation.org \
--cc=kniht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=support@osuosl.org \
--cc=users@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
Powered by JetHome