public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Harsha Goli <harshagoli@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] CTV + CSFS: a letter
Date: Wed, 11 Jun 2025 17:59:27 -0700 (PDT)	[thread overview]
Message-ID: <de023ffa-6f8b-44bc-8e4d-6012e2ba3ccen@googlegroups.com> (raw)
In-Reply-To: <46349b6c-ccec-4378-8721-aecec22752e7@mattcorallo.com>


[-- Attachment #1.1: Type: text/plain, Size: 1716 bytes --]

Hi Matt

> What a wonderful way to discourage people from working with you in the 
strongest possible way.
> 
> Starting with vague threats is quite a strategy.

Quickly chiming in here. I'm digging in heavily to the different needs and 
drivers of businesses and individuals in the space. I think James is being 
quite literal here. There is not unity on what should happen after if we 
reach 2026 without any progress on covenants.

Not speaking for James, but from what I've seen there is no substance or 
chatter regarding any such "vague threat".

Hope that clears up this unfortunate misunderstanding.

On Wednesday, June 11, 2025 at 8:02:15 PM UTC-4 Matt Corallo wrote:

>
>
> On 6/11/25 12:50 PM, James O'Beirne wrote:
> > Greg,
> > 
> > > Just noting that the "what is the ultimatum" section is still a
> > > standing question
> > 
> > I think this is outside the scope of the letter and this discussion -
> > different cosigners will have different ideas about what should happen
> > if another 6 months goes by without a serious attempt at review and
> > integration. We'll cross that bridge when/if we come to it.
>
> What a wonderful way to discourage people from working with you in the 
> strongest possible way.
>
> Starting with vague threats is quite a strategy.
>
> Matt
>

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/de023ffa-6f8b-44bc-8e4d-6012e2ba3ccen%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2388 bytes --]

  reply	other threads:[~2025-06-12  1:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 11:40 James O'Beirne
2025-06-09 12:51 ` Michael Folkson
2025-06-09 14:41   ` James O'Beirne
2025-06-09 15:56     ` Michael Folkson
2025-06-09 13:51 ` Matt Corallo
2025-06-09 14:43   ` James O'Beirne
2025-06-09 17:51     ` Matt Corallo
2025-06-09 19:27       ` /dev /fd0
2025-06-09 21:12         ` Matt Corallo
2025-06-09 18:55 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10  2:02   ` Paul Sztorc
2025-06-09 23:02 ` Andrew Poelstra
2025-06-10  2:08   ` David A. Harding
2025-06-10 13:23     ` Andrew Poelstra
2025-06-10 17:17       ` Matt Corallo
2025-06-10 23:42         ` Antoine Riard
2025-06-12  3:34           ` James O'Beirne
2025-06-10 23:42         ` Antoine Riard
2025-06-11 13:52         ` Peter Todd
2025-06-10 14:03     ` James O'Beirne
2025-06-10 16:56       ` Sjors Provoost
2025-06-10 17:15         ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10 19:04         ` Paul Sztorc
2025-06-11 18:09         ` Brandon Black
2025-06-10  2:28   ` Melvin Carvalho
2025-06-10 13:19     ` Greg Sanders
2025-06-11 14:12       ` James O'Beirne
     [not found]         ` <CAB3F3Dsf8=rbOyPf1yTQDzyQQX6FAoJWTg16VC8PVs4_uBkeTw@mail.gmail.com>
2025-06-11 16:50           ` James O'Beirne
2025-06-11 18:34             ` James O'Beirne
2025-06-11 20:30             ` Matt Corallo
2025-06-12  0:59               ` Harsha Goli [this message]
2025-06-12 18:04                 ` Matt Corallo
2025-06-12 18:38                   ` James O'Beirne
2025-06-12 18:43                     ` Matt Corallo
2025-06-12 19:51                     ` Andrew Poelstra
2025-06-12 22:44                       ` Matt Corallo
2025-06-12  2:06 ` Greg Maxwell
2025-06-12  3:23   ` James O'Beirne

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=de023ffa-6f8b-44bc-8e4d-6012e2ba3ccen@googlegroups.com \
    --to=harshagoli@gmail$(echo .)com \
    --cc=bitcoindev@googlegroups.com \
    /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