From: Tiu <putr@his.org>
To: info-gnus-english@gnu.org
Subject: Re: long lines in followups
Date: Fri, 15 Mar 2013 17:23:00 +0100 [thread overview]
Message-ID: <84sj3wr5sr.fsf@his.org> (raw)
In-Reply-To: <84d2v0myoj.fsf@his.org>
Tiu <putr@his.org> writes:
> Oh ok, but I've to enter the sequence when looking at the article body
> right? I'll try again then.
Ok, was tryin while editing the message that's why was not working.
next prev parent reply other threads:[~2013-03-15 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 0:56 Tiu
2013-03-15 14:49 ` Corey Wells
2013-03-15 16:10 ` Tiu
2013-03-15 16:23 ` Tiu [this message]
2013-03-15 21:01 ` Corey Wells
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=84sj3wr5sr.fsf@his.org \
--to=putr@his.org \
--cc=info-gnus-english@gnu.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).