From: Yao Qi <yao@codesourcery.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: Unable to send mail/patch to gdb-patches@sourceware.org
Date: Thu, 16 Jun 2011 12:35:00 -0000 [thread overview]
Message-ID: <4DF9F88E.7040001@codesourcery.com> (raw)
In-Reply-To: <20110616111919.GB12477@redhat.com>
On 06/16/2011 07:19 PM, Frank Ch. Eigler wrote:
> Hi -
>
> On Thu, Jun 16, 2011 at 10:59:01AM +0800, Yao Qi wrote:
>> Today and yesterday, I sent the same mail twice to
>> gdb-patches@sourceware.org, but I don't see gdb-patches@ get them. [...]
>
> I see two messages from you to gdb-patches. Can we infer that the problem
> fixed itself? (It may have been a problem on the codesourcery side.)
>
Yes, these two mails show up this afternoon, delayed for many hours. I
am not sure it is a codesourcery's mail problem, because I was able to
send out mail to my gmail box. Anyway, problem goes away. Thanks.
--
Yao (é½å°§)
prev parent reply other threads:[~2011-06-16 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 2:59 Yao Qi
2011-06-16 11:19 ` Frank Ch. Eigler
2011-06-16 12:35 ` Yao Qi [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=4DF9F88E.7040001@codesourcery.com \
--to=yao@codesourcery.com \
--cc=fche@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).