From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] About newlines
Date: Fri, 04 Apr 2008 14:14:06 +0200 [thread overview]
Message-ID: <1207309393-sup-2829@ausone.inria.fr> (raw)
I'm hitting a bug concerning forwarding, all newlines get trimmed off. I'm
trying to fix the bug, but I don't understand if arrays of lines are supposed
to be ended by newlines or not.
--
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080404/acbb1193/attachment.bin
next reply other threads:[~2008-04-04 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 12:14 Nicolas Pouillard [this message]
2008-04-04 16:08 ` William Morgan
2008-04-04 16:10 ` Nicolas Pouillard
2008-04-04 16:16 ` Marc Hartstein
2008-04-04 13:13 kendall at clarkparsia.com
2008-04-04 16:17 kendall at clarkparsia.com
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=1207309393-sup-2829@ausone.inria.fr \
--to=nicolas.pouillard@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox