From: Matt Corallo <lf-lists@mattcorallo.com>
To: Juan Aleman <bitcoindev@juanaleman.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [Pre-BIP Discussion] Bitcoin Node Repository Consensus-Policy Separation
Date: Fri, 31 Oct 2025 14:36:09 -0400 [thread overview]
Message-ID: <16007942-114D-4183-9CBB-BEEEF70E5F41@mattcorallo.com> (raw)
In-Reply-To: <d397e2e1-3d5b-473a-b915-aca2cfc9da32n@googlegroups.com>
[-- Attachment #1: Type: text/html, Size: 7414 bytes --]
next prev parent reply other threads:[~2025-10-31 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 17:54 Juan Aleman
2025-10-31 18:21 ` Greg Maxwell
2025-10-31 18:32 ` Juan Aleman
2025-10-31 18:47 ` Greg Maxwell
2025-10-31 18:56 ` Juan Aleman
2025-10-31 22:59 ` Antoine Riard
2025-11-01 15:59 ` Juan Aleman
2025-11-01 17:54 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-11-02 20:04 ` Antoine Riard
2025-11-02 20:43 ` Juan Aleman
2025-10-31 18:36 ` Matt Corallo [this message]
2025-10-31 18:51 ` Juan Aleman
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=16007942-114D-4183-9CBB-BEEEF70E5F41@mattcorallo.com \
--to=lf-lists@mattcorallo.com \
--cc=bitcoindev@googlegroups.com \
--cc=bitcoindev@juanaleman.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