public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/43011] Upgrade gcc.gnu.org/bugzilla to Bugzilla 3.6
Date: Thu, 16 Sep 2010 22:51:00 -0000	[thread overview]
Message-ID: <20100916225115.27505.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43011-18765@http.gcc.gnu.org/bugzilla/>



------- Comment #49 from LpSolit at netscape dot net  2010-09-16 22:51 -------
(In reply to comment #48)
> The current bugzilla has
> extra separating lines with the column names. The new installation does not. 

Yeah, it is so by design. Not something I'm going to reimplement.

Note that we finally won't upgrade tomorrow. I have severe hardware failures
with my PC, and I cannot reliably run the upgrade process under these
conditions. It's a miracle when I can comment in a bug without seeing my PC
shut down for no reason. Sorry about that.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43011

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

  parent reply	other threads:[~2010-09-16 22:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43011-18765@http.gcc.gnu.org/bugzilla/>
2010-06-28 23:42 ` ian at airs dot com
2010-07-15 23:04 ` LpSolit at netscape dot net
2010-07-19 12:00 ` dberlin at dberlin dot org
2010-08-09 22:21 ` LpSolit at netscape dot net
2010-09-07 14:59 ` LpSolit at netscape dot net
2010-09-07 16:16   ` Christopher Faylor
2010-09-07 15:51 ` tromey at gcc dot gnu dot org
2010-09-07 16:16 ` gerald at pfeifer dot com
2010-09-07 16:17 ` gerald at pfeifer dot com
2010-09-07 16:23 ` LpSolit at netscape dot net
2010-09-07 17:45 ` tom dot browder at gmail dot com
2010-09-07 17:58 ` tom dot browder at gmail dot com
2010-09-07 18:11 ` LpSolit at netscape dot net
2010-09-07 18:17 ` fche at redhat dot com
2010-09-07 21:38 ` fche at redhat dot com
2010-09-07 22:50 ` dberlin at dberlin dot org
2010-09-07 22:54 ` LpSolit at netscape dot net
2010-09-08 21:36 ` LpSolit at netscape dot net
2010-09-09 22:43 ` LpSolit at netscape dot net
2010-09-10  9:34 ` rguenth at gcc dot gnu dot org
2010-09-10  9:58 ` jv244 at cam dot ac dot uk
2010-09-10 10:29 ` burnus at gcc dot gnu dot org
2010-09-10 10:34 ` LpSolit at netscape dot net
2010-09-10 10:46 ` jakub at gcc dot gnu dot org
2010-09-12 20:24 ` LpSolit at netscape dot net
2010-09-15 21:17 ` LpSolit at netscape dot net
2010-09-16 22:51 ` LpSolit at netscape dot net [this message]
2010-09-20 21:43 ` LpSolit at netscape dot net
2010-09-20 21:47 ` LpSolit at netscape dot net
2010-09-22 20:16 ` LpSolit at netscape dot net
2010-09-22 20:18 ` LpSolit at netscape dot net
     [not found] <bug-43011-5127@http.gcc.gnu.org/bugzilla/>
2010-09-24 11:51 ` manu at gcc dot gnu.org
2010-09-24 16:36 ` LpSolit at netscape dot net
2010-09-24 21:34 ` tromey at gcc dot gnu.org
2010-09-24 21:39 ` LpSolit at netscape dot net
2010-09-24 21:50 ` steven at gcc dot gnu.org
2010-09-24 21:58 ` gerald at pfeifer dot com
2010-09-25 16:58 ` LpSolit at netscape dot net
2010-09-25 17:02 ` LpSolit at netscape dot net
2016-08-16 15:42 ` ovxr at barryogorman dot com

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=20100916225115.27505.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).