4 ms·
> Only because I've read this story more than a few times before? See: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22bcachefs%22%20merge&sor
by m45t3r 3y ago
> Only because I've read this story more than a few times before? See: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22bcachefs%22%20merge&sort=byPopularity&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
Sorry, if we are looking at the same thing, the earliest time of a HN entry of bcachefs trying to be merged upstream was not even 1 month ago. All the other entries are related to features that are called "merge" and not actual merge requests or the author declaring that the code was up to be merged but not an actual merge request.
1 month ago is nothing in terms of kernel time, so I don't think your argument holds up.
- viraptor 3y agoThere was a previous attempt 4 years ago. It's normal that there's some pushback and things get worked on for some more time. Nothing that indicates a serious problem here. Kent worked on the filesystem overall rather than addressing the comments and resubmitting immediately. (But that's still a single initial attempt, not "a few" like the OP claimed)
- mustache_kimono 3y agoI can't believe I have to say this to people. Before you nit pick, expand your search parameters? See: https://news.ycombinator.com/item?id=17138877 https://news.ycombinator.com/item?id=17138877
- Dylan16807 3y agoThat article says "An update on bcachefs" and "it is time to start talking about getting the code upstream". The article also makes it clear that it's not ready. And for a big patch like this, you're going to "start talking" long before actually submitting. The only thing that supports your point is the incorrect title that was submitted to HN. But this submission got 6 upvotes and 0 comments, so almost nobody saw this title.