From: guillaume.quintard@gmail.com (Guillaume Quintard)
Subject: [sup-talk] Carriage return
Date: Fri, 19 Jun 2009 13:27:50 +0200 [thread overview]
Message-ID: <1245410627-sup-2801@altis> (raw)
Sup seems to work smoothly now (no noticeable problem with the sent label, hoorray!!) (not complaining since I'm using the next branch). Now I'd like to fix one little annoying thing: in case of error, messages will use the newline, but not the carriage return, meaning mutiple lines messages will appear like this:
yadda yadda
yadda yadda yadda yadda
yadda yadda
Is there a way to fix that?
--
Guillaume
next reply other threads:[~2009-06-19 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 11:27 Guillaume Quintard [this message]
2009-06-19 13:51 ` Andrei Thorp
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=1245410627-sup-2801@altis \
--to=guillaume.quintard@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