ylyn

You assert that ECC RAM being necessary for ZFS is just a myth but provide no justification for why that is untrue.

Is it not the case that if you don't have ECC memory, ZFS could end up writing a checksum that does not match the data if you get a bitflip in just the right (wrong) spot?

One pitfall of this is that the decompressed contents of your initramfs must fit within half of your physical RAM since Linux decompresses it into a tmpfs.

Or if you set rootfstype=ramfs, then you can take up to all of physical RAM, but ramfs isn't swappable.

I'm very confused by your comment. The grandparent comment talks about using the gitrevisions syntax in a GitHub URL to search the reflog stored on GitHub. Nothing to do with your local clone of a repository.

Last I checked it didn't even have a notion of currency, let alone multiple currencies.

That's not a reasonable requirement at all. A common recommendation nowadays is to have passphrases..

I just received mine. It's indeed great!

Wait till you forget your password one day.

Firefox has way too many components to be "just one repo you can fork".

> They're the ones who have normalised constant churn and thus needing to keep drivers for hardware, sometimes many years old, up to date year after year or even month after month.

That's exactly why you should mainline your code. Then people refactoring other subsystems will fix your code for you.

I can't believe people are trying to extrapolate this situation into how someone would act as a manager in a company.

Can't you see that the kernel has its own conventions and practices that are entirely different from typical corporate practices?

> A patch is a patch and the author should be credited as such.

But the patch was not taken. The maintainer fixed it a different way. So credit is given for reporting the issue and suggesting a fix, and that is what is represented by the Reported-By. Is that so hard to understand?