From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: <overseers@gcc.gnu.org>, Neil Booth <neil@daikokuya.co.uk>
Subject: Re: GNATS restore PRs 1 and 2182
Date: Thu, 02 Jan 2003 11:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0301021106360.16131-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <Pine.BSF.4.51.0301020944190.29516@acrux.dbai.tuwien.ac.at>
On Thu, 2 Jan 2003, Gerald Pfeifer wrote:
> When adding two new GNATS categories (driver and inline-asm) I,
> botched and failed to update directory permissions of the two new
> directories.
>
> Unfortuntely, the failure mode of GNATS when there is such a problem
> moving a PR into a new category heavily sucks: the PR simply gets lost!
I hope the GNATS maintainers know of this problem (and of that when the
disk gets full): it's still relevant to other GNATS users after GCC moves
to Bugzilla (even if all the projects using GNATS on sourceware switch as
well).
(I also hope that Bugzilla/MySQL fails safe when there are configuration
errors, disk full, ..., so switching will fix these problems.)
--
Joseph S. Myers
jsm28@cam.ac.uk
prev parent reply other threads:[~2003-01-02 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 8:48 Gerald Pfeifer
2003-01-02 11:09 ` Joseph S. Myers [this message]
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=Pine.LNX.4.33.0301021106360.16131-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=neil@daikokuya.co.uk \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).