public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Proposal: Disable digests on bitcoin-dev
Date: Mon, 31 Aug 2015 15:27:24 -0700	[thread overview]
Message-ID: <CAEz79PoGiQc7yJckwEacNtEP_OSMUr3+yyHQTM0UgKBuRzFhfQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

Hi folks,

I think we should agree to disable the ability to subscribe with digests on
bitcoin-dev list.  I think digests were from an earlier era of Internet
history.  Digests are inconvenient for everyone because replies have the
problem of breaking threads.    These days people should be setting mail
filters to separate list mail from other mail.  I think digests are really
not a net-positive for the community so we should just turn off the ability
to do it.

Any objections?

Warren Togami

[-- Attachment #2: Type: text/html, Size: 628 bytes --]

             reply	other threads:[~2015-08-31 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 22:27 Warren Togami Jr. [this message]
2015-08-31 23:46 ` [bitcoin-dev] Proposal: Disable digests on bitcoin-dev Augusto Radtke

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=CAEz79PoGiQc7yJckwEacNtEP_OSMUr3+yyHQTM0UgKBuRzFhfQ@mail.gmail.com \
    --to=wtogami@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.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