Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by zwischenzug on Sunday July 21, 2019 @02:23PM
(#20492819)
Usually I've ventured into the code and made a bad enough attempt to fix that the devs are galvanised into doing it right. Filing a ticket usually not enough table stakes to get your voice heard if things are worked around.
[ Parent
| on HN ]
Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by stallmanite on Sunday July 21, 2019 @05:12PM
(#20493706)
I like this concept. I wonder if there’s a word for it. Any Germans want to help out with a fifteen syllable wonder?
Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by OJFord on Sunday July 21, 2019 @05:33PM
(#20493803)
Tikettfileninsufficientstadtdelvencodebasefixen.
Or something? More seriously, relevant English idioms:
- A stitch in time saves nine;
- Something worth doing's worth doing well;
- If you want it done right, do it yourself;
and surely more. I'm certain there's a farming-analogy one about fixing something sooner rather than later, but it's escaped me.
Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by twic on Sunday July 21, 2019 @08:07PM
(#20494515)
So, we've got:
Cunningham's Law: "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer" [1]
"Broke gets fixed, crappy is forever" [2]
I feel like there should be a third but that's what i've got.
[1] http://fed.wiki.org/journal.hapgood.net/cunninghams-law/fora...
[2] https://dandreamsofcoding.com/2013/05/06/broke-gets-fixed-cr...
Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by Izkata on Monday July 22, 2019 @06:36PM
(#20502929)
Maybe something about the dummy fix polluting the lead dev's code aesthetics?
Re:Fsyncgate: Errors on fsync are unrecoverable (2018)
by tgsovlerkhgsel on Sunday July 21, 2019 @07:02PM
(#20494233)
Threat-in-a-patch