Published on: 2011-12-21T17:37:39+00:00
In response to Gavin's announcement, Luke-Jr mentioned that he had already merged 21 branches into his 'next' and 'next-test' branches, which included accepted, ready for acceptance, and branches that required review. He also listed some branches that could not be merged cleanly at that point and branches that were yet to be written. These branches covered various features and improvements for Bitcoin version 0.6.During the discussion between Luke-Jr and Jeff Garzik, Luke-Jr claimed that the feature called "Coinbaser" had been accepted for version 0.6, but Garzik disagreed and emphasized the need for buy-in from other miners. Luke-Jr mentioned that Eclipse and slush were already using Coinbaser, with slush intending to use it.In another email exchange, Jeff Garzik expressed his disagreement with a change proposed by Luke-Jr related to coinbaser for the 0.6 version of a software. Garzik reminded Luke-Jr about the importance of getting buy-in from other miners and making decisions based on what they want rather than personal preferences. Luke-Jr responded by stating that there was support from other miners for the change and that Gavin had approved it on IRC.Additionally, Mike Hearn raised a concern about Git not producing helpful summaries when every commit is a merge. Someone suggested using the command `git log --no-merges` as a potential solution to address this issue.Overall, the context provides insights into the development process of Bitcoin version 0.6, including discussions about feature acceptance, the importance of buy-in from other miners, and challenges related to Git's lack of helpful summaries for merges.
Updated on: 2023-08-01T02:46:55.172831+00:00