06:38 <achow101> instagibbs: is there a purpose to having it opened but locked? If it's not ready for discussion yet, then I think you should just wait to open the PR when it is ready.

06:59 <gmaxwell> his op_return but keeping the setting? it's been productive to public discussion because it shows there is an alternative proposed for those people who are *only* unhappy about removing a knob.

07:00 <gmaxwell> I just saw a reddit post making that point: https://old.reddit.com/r/Bitcoin/comments/1kea81d/why_is_this_sub_quiet_about_the_current_debate/mqhy0bo/

07:26 <achow101> Yeah, but it can't be something that's being seriously considered if no one can comment on it.

07:31 <gmaxwell> if you close it would be helpful to note that it isn't being closed because it's a non-starter or being abandoned, just because it's not ready for comments. (I'm just thinking in terms of how people might misrepresent the closure, it's generally free to provide more context).

09:45 <Earnestly> Or, open it and let people discuss however they like

13:06 <bitcoin-git> [bitcoin] maflcko closed pull request #29678: Bugfix: Correct first-run free space checks (master...fix_init_lowdisk_warning_reqd) https://github.com/bitcoin/bitcoin/pull/29678

13:06 <bitcoin-git> [bitcoin] maflcko reopened pull request #29678: Bugfix: Correct first-run free space checks (master...fix_init_lowdisk_warning_reqd) https://github.com/bitcoin/bitcoin/pull/29678

14:08 <bitcoin-git> [bitcoin] andrewtoth reopened pull request #32414: validation: periodically flush dbcache during reindex-chainstate (master...reindex-flush) https://github.com/bitcoin/bitcoin/pull/32414