From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] STS
Date: Sun, 19 Oct 2008 19:38:13 -0700 [thread overview]
Message-ID: <1224470147-sup-7715@entry> (raw)
In-Reply-To: <76D7DBC9-339A-490F-9DF5-F186E014B99D@gmail.com>
Reformatted excerpts from fedzor's message of 2008-10-15:
> In STS, will it be delivering messages itself? Is there a reason why
> it shouldn't? If it should be done, I'd be more than happy to add that
> ability.
The server part won't, but clients may choose to. I'm planning on doing
the minimum to port the current curses client over, so if you really
want that in STS, you could just add it there. Personally I'm happy to
have sendmail do all the hard work for me, but I understand that that
complicates some people's setup.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-10-20 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 1:43 fedzor
2008-10-20 2:38 ` William Morgan [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=1224470147-sup-7715@entry \
--to=wmorgan-sup@masanjin.net \
/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