From: Gavin Andresen <gavinandresen@gmail•com>
To: Matt Corallo <bitcoin-list@bluematt•me>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Forking personal "vanity" versions...
Date: Fri, 29 Jul 2011 08:41:12 +1000 [thread overview]
Message-ID: <CABsx9T1c+dE2NESPEPVv8LYEeJ0b285+-Duj-eKRomV+c4ZEaw@mail.gmail.com> (raw)
In-Reply-To: <1311881309.2380.1.camel@Desktop666>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
Matt: First I agree with you. Second: your should have sent your message
directly to Alan instead of to the entire bitcoin-development list.
All: The idea is for this mailing list to be CONSTRUCTIVE discussion of
bitcoin development. Please ask yourself "will my message help move the
bitcoin project forward or will it just make somebody angry" before posting.
And assume that at least someone on the list just broke up with their
girlfriend and is in a crappy mood.
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 573 bytes --]
prev parent reply other threads:[~2011-07-28 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 18:43 Alan Grimes
2011-07-28 18:49 ` Gregory Maxwell
2011-07-28 18:58 ` John Smith
2011-07-28 19:08 ` Luke-Jr
2011-07-28 19:28 ` Matt Corallo
2011-07-28 22:41 ` Gavin Andresen [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=CABsx9T1c+dE2NESPEPVv8LYEeJ0b285+-Duj-eKRomV+c4ZEaw@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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