From: James Bulpin <james@xensource.com>
To: xen-devel <xen-devel@lists.xensource.com>,
xen-changelog@lists.xensource.com
Subject: xen-changelog madness
Date: Mon, 15 Aug 2005 16:59:44 +0100 [thread overview]
Message-ID: <4300BBF0.2040200@xensource.com> (raw)
Folks,
Apologies to those of you who subscribe to xen-changelog for the large
number of resent messages you received today. We added another volume to
xenbits.xensource.com; the move of the data from one volume to the other
wasn't as atomic as hoped and it looks like the patchbot last-mailed
file got moved shortly after the patchbot script started but before it
checked that file. Just goes to show the importance of avoiding race
conditions.
Regards,
James
reply other threads:[~2005-08-15 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4300BBF0.2040200@xensource.com \
--to=james@xensource.com \
--cc=xen-changelog@lists.xensource.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.