public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: William Yager <will.yager@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Bitcoin Core trial balloon: splitting blockchain engine and wallet
Date: Fri, 21 Feb 2014 07:54:01 +0100	[thread overview]
Message-ID: <CA+s+GJC+1Dxa1bJ_CBQjZ6x=hb6yKbe9x3c6haQDzQvhkbYJOg@mail.gmail.com> (raw)
In-Reply-To: <AB055C1C-76B1-4CE3-B92E-253C1C9541F6@gmail.com>

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

On Fri, Feb 21, 2014 at 7:50 AM, William Yager <will.yager@gmail.com> wrote:

> Running the network part of the core as a system service might make sense
> for server implementations, but it’s a pain in the rear for most users.
>

Come on, making it a possibility doesn't affect other kinds of use cases in
any way. Are you just arguing for the sake of arguing?

Wladimir

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

  reply	other threads:[~2014-02-21  6:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  6:09 [Bitcoin-development] Bitcoin Core trial balloon: splitting blockchain engine and wallet Jeff Garzik
2014-02-21  6:27 ` Mike Hearn
     [not found]   ` <CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
2014-02-21  6:43     ` [Bitcoin-development] Fwd: " Wladimir
2014-02-21  6:50       ` William Yager
2014-02-21  6:54         ` Wladimir [this message]
2014-02-22  1:09       ` Dustin D. Trammell
2014-02-22  6:53         ` Wladimir
2014-02-24 22:16           ` James Hartig
2014-02-21  6:50   ` [Bitcoin-development] " Jeff Garzik
2014-02-21 10:41     ` Mike Hearn
2014-02-21 11:06       ` Peter Todd
2014-02-22  1:04 ` Dustin D. Trammell
2014-02-22  2:08   ` Jeff Garzik

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='CA+s+GJC+1Dxa1bJ_CBQjZ6x=hb6yKbe9x3c6haQDzQvhkbYJOg@mail.gmail.com' \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=will.yager@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