public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Dave Scotese <dscotese@litmocracy.com>, xor@freenetproject.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Three Month bitcoin-dev Moderation Review
Date: Thu, 21 Jan 2016 15:30:20 +1030	[thread overview]
Message-ID: <87bn8fy1az.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAGLBAhd7DCcRiJ6SZvJ9hEBWvBnmgRWKLL00yxaeiGSEbNKNwQ@mail.gmail.com>

Dave Scotese via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> writes:
> It is a shame that the moderated messages require so many steps to
> retrieve.  Is it possible to have the "downloadable version" from
> https://lists.ozlabs.org/pipermail/bitcoin-dev-moderation/ for each month
> contain the text of the moderated emails?  They do contain the subjects, so
> that helps.

Yes, it's because we simply forward them to the bitcoin-dev-moderation
mailing list, and it strips them out as attachments.

I'd really love a filter which I could run them through (on ozlabs.org)
to fix this.  Volunteers welcome :)

Cheers,
Rusty.


  reply	other threads:[~2016-01-21  5:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21  0:50 [bitcoin-dev] Three Month bitcoin-dev Moderation Review Rusty Russell
2016-01-21  2:25 ` xor
2016-01-21  4:35   ` Dave Scotese
2016-01-21  5:00     ` Rusty Russell [this message]
2016-01-21  4:44   ` Rusty Russell
2016-01-23  5:33     ` xor
2016-01-23 20:59       ` Peter Todd
2016-01-23 21:38         ` Gavin
2016-01-24  1:06           ` Dave Scotese
2016-02-09 23:24             ` David Vorick

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=87bn8fy1az.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=dscotese@litmocracy.com \
    --cc=xor@freenetproject.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