From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] flexible sent source (update)
Date: Wed, 13 May 2009 11:11:10 -0700 [thread overview]
Message-ID: <1242238048-sup-6168@entry> (raw)
In-Reply-To: <1241733502-sup-26@ntdws12.chass.utoronto.ca>
Hi Ben,
Reformatted excerpts from Ben Walton's message of 2009-05-07:
> I'd appreciate it if those interested in the topic played with this
> branch. William, I'd also appreciate any feedback you have on it at
> this point. (Do you mind pulling my branch, or would you prefer a
> git-send-email stack of patches?)
This branch looks great. Thanks! We're going to have to rebase it
against master before merging in, but I think that will be easier once I
merge a few other branches down from next to master.
> I still need to tackle mbox locking...
This is puntable for now, if we make it clear to the user that their
sent box shouldn't also receive mail.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-05-13 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 22:01 Ben Walton
2009-05-13 18:11 ` William Morgan [this message]
2009-05-13 18:50 ` Ben Walton
2009-05-13 18:55 ` William Morgan
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=1242238048-sup-6168@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