From: Jim Meyering <jim@meyering.net>
To: "Alasdair G. Kergon" <agk@redhat.com>
Cc: overseers@sourceware.org
Subject: sourceware.org's web server is not responding
Date: Tue, 25 Sep 2007 09:08:00 -0000 [thread overview]
Message-ID: <878x6vru2o.fsf@rho.meyering.net> (raw)
Hi Alasdair,
[now, I see that it's not specific to LVM2 or your commit/log hook]
I've just committed a tiny LVM2 typo fix like this:
$ cvs commit -F .msg doc/testing.txt
Checking in doc/testing.txt;
/cvs/lvm2/LVM2/doc/testing.txt,v <-- testing.txt
new revision: 1.2; previous revision: 1.1
done
500 read timeout from http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/testing.txt.diff?cvsroot=lvm2&r1=1.1&r2=1.2
Note the final diagnostic.
Between the commit and the diagnostic there was a long delay.
It didn't affect the commit, since your script is run only on the
cvs post-commit log hook, of course, but it is disconcerting to see
a "cvs commit" appear to hang.
I've just dug a little depeer and see that sourceware's web
server is not responding:
sourceware$ nc -w2 localhost 80
[Exit 1]
I can't help with that, but overseers (Cc'd) surely can.
Jim
P.S., Once lvm switches to git, it'll be trivial to include the diff output
in the email-to-list message without having to go through a web server.
next reply other threads:[~2007-09-25 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 9:08 Jim Meyering [this message]
2007-09-25 10:41 ` Jonathan Larmour
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=878x6vru2o.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=agk@redhat.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).