From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: No newline at the end of the article with broken MIME message
Date: Wed, 14 Jun 2006 20:45:42 +0900 [thread overview]
Message-ID: <b4mslm8x8nt.fsf@jpl.org> (raw)
In-Reply-To: <v9k67knhga.fsf@marauder.physik.uni-ulm.de>
>>>>> In <v9k67knhga.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib wrote:
> On Wed, Jun 14 2006, Katsumi Yamaoka wrote:
>> I found the MIME messages[1] in the emacs-devel list that seem
>> to have been broken.
[...]
> IMHO it would be good to post messages like this[1] to ding as well[2]
> because it's by far more convenient to find an article in the archive
> of gmane.emacs.gnus.general on Gmane than in gnus.gnus-bug. WDYT?
> Bye, Reiner.
> [1] Or e.g. <news:b4mmzck8quc.fsf@jpl.org>
> [2] Either only to ding or cc-ing ding.
I agree. Though I thought that such a trivial issue was not
worth posting to the ding list, who judges whether it is
important or not will probably be the audience. :)
prev parent reply other threads:[~2006-06-14 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b4mzmggxdpp.fsf@jpl.org>
2006-06-14 10:45 ` Reiner Steib
2006-06-14 11:45 ` Katsumi Yamaoka [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=b4mslm8x8nt.fsf@jpl.org \
--to=yamaoka@jpl.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 NNTP newsgroup(s).