š
Original date posted:2011-08-11
šļø Summary of this message: A discussion on backward compatibility in Bitcoin development, with one participant suggesting a single release for all changes instead of incremental updates.
š Original message:On 2011 August 11 Thursday, Joel Joonatan Kaartinen wrote:
> On Thu, 2011-08-11 at 06:47 +0100, Andy Parkins wrote:
> > Again you're missing my point... you are still shooting ideas down.
>
> And you're only shooting his actions down without indicating clearly
Yeah, shooting down a shooting down, which you've just shot down. Where will
it end?
> what you think ought to be done instead. What do you want him to say
> instead?
How about:
"This is a good idea, but we don't want to break backward compatibility a
little piece at a time. Instead we'd like to collect all such changes into
one single compatibility breaking release. Here's the wiki page you should
update; and here's the git branch you should push changes like this to."
> most suggestions you point at have been discussed about before
I know the application/protocol version split has been discussed before, but
please point me to the relevant discussion on: loading the block chain in
reverse; transaction only requests; checksumming removal; verack removal;
storing script parameters outside the script; and requesting blocks by
transaction hash instead of block hash.
If I've missed all of these discussions and their inevitable logically
indisputable rejection, I apologise.
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110811/bc780656/attachment.sig>;
Andy Parkins [ARCHIVE] /
npub1nxā¦7wjrv
2023-06-07 02:14:36
in reply to nevent1qā¦4cy7
Author Public Key
npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrvSeen on
wss://relay.nostr.bandPublished at
2023-06-07 02:14:36Event JSON
{
"id": "08a3bd64b40cf77aee0ae20e455cf33c8d5eda7a51e01a1759409408732f3cfb",
"pubkey": "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59",
"created_at": 1686104076,
"kind": 1,
"tags": [
[
"e",
"fe8ae56772ad6135ef8f3cc5e223de1011f21616a51d5302085d2b9ebf339345",
"",
"root"
],
[
"e",
"7d6e3170b161ff86ddcc4a40a27c0cf35240955216b94063aa8f8894e439febd",
"",
"reply"
],
[
"p",
"72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057"
]
],
"content": "š
Original date posted:2011-08-11\nšļø Summary of this message: A discussion on backward compatibility in Bitcoin development, with one participant suggesting a single release for all changes instead of incremental updates.\nš Original message:On 2011 August 11 Thursday, Joel Joonatan Kaartinen wrote:\n\u003e On Thu, 2011-08-11 at 06:47 +0100, Andy Parkins wrote:\n\u003e \u003e Again you're missing my point... you are still shooting ideas down.\n\u003e \n\u003e And you're only shooting his actions down without indicating clearly\n\nYeah, shooting down a shooting down, which you've just shot down. Where will \nit end?\n\n\u003e what you think ought to be done instead. What do you want him to say\n\u003e instead?\n\nHow about:\n\n\"This is a good idea, but we don't want to break backward compatibility a \nlittle piece at a time. Instead we'd like to collect all such changes into \none single compatibility breaking release. Here's the wiki page you should \nupdate; and here's the git branch you should push changes like this to.\"\n\n\u003e most suggestions you point at have been discussed about before\n\nI know the application/protocol version split has been discussed before, but \nplease point me to the relevant discussion on: loading the block chain in \nreverse; transaction only requests; checksumming removal; verack removal; \nstoring script parameters outside the script; and requesting blocks by \ntransaction hash instead of block hash.\n\nIf I've missed all of these discussions and their inevitable logically \nindisputable rejection, I apologise.\n\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 198 bytes\nDesc: This is a digitally signed message part.\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110811/bc780656/attachment.sig\u003e",
"sig": "8b26f57b6d15d260dece90c80d0bc5d5346f12eeda20f16f84db518a29b13d40e8fd5038374ac5cce9e845ad491fafdec45bb598091c1007b24756fdfc5bb677"
}