From: Ian Lance Taylor <iant@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: overseers@sourceware.org
Subject: Re: Is sourceware email/bugzilla dead?
Date: Fri, 01 Oct 2010 18:20:00 -0000 [thread overview]
Message-ID: <mcr4od5lqq1.fsf@google.com> (raw)
In-Reply-To: <AANLkTimhqUuDJHyeVWBLYJtkCtwaxx113f90YErxxw7k@mail.gmail.com> (H. J. Lu's message of "Thu, 30 Sep 2010 22:12:19 -0700")
"H.J. Lu" <hjl.tools@gmail.com> writes:
> I checked in 2 patches:
>
> http://sourceware.org/ml/binutils-cvs/2010-10/msg00002.html
> http://sourceware.org/ml/binutils-cvs/2010-10/msg00003.html
>
> But they didn't show up in
>
> http://lists.gnu.org/archive/html/bug-binutils/
sourceware.org/bugzilla is not dead.
The CVS commit message was forwarded to Bugzilla as it should have
been. It failed when trying to add the data to Bugzilla:
mlcheck:_spam_detected_-_exit_status_n=1,_0Content-type:_text/html//<h1>Software_error:</h1>/<pre>can't_write_to_directory_at_/www/sourceware/bugzilla/contrib/bugzilla_email_append.pl_line_50./</pre>/<p>/For_help,_please_send_mail_to_this_site's_webmaster,_giving_this_error_message_/and_the_time_and_date_of_the_error.//</p>/[Thu_Sep_30_10:24:57_2010]_bugzilla_email_append.pl:_can't_write_to_directory_at_/www/sourceware/bugzilla/contrib/bugzilla_email_append.pl_line_50./did_0+0+2/
I believe this means that the script
/www/sourceware/bugzilla/contrib/bugzilla_email_append.pl
found that it could not write to the directory
/www/sourceware/bugzilla/data/mimedump-tmp
Ian
prev parent reply other threads:[~2010-10-01 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 5:12 H.J. Lu
2010-10-01 18:20 ` Ian Lance Taylor [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=mcr4od5lqq1.fsf@google.com \
--to=iant@google.com \
--cc=hjl.tools@gmail.com \
--cc=overseers@sourceware.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).