[thayne]

I've contributed to a couple of projects that use email based workflows. I can customize my environment, but it takes a lot of time, and I would rather do something else than figure out how to filter the firehose of a mailing list to the few emails I actually care about, or learn how to use a new email client that is slightly better and handling patches.

The first few times, it took me longer to figure out how to send a patch than it did to fix the bug I was writing a patch for.

[db48x]

But you only have to figure that out once. Amortized over many contributions the cost is essentially nothing.

[solarkraft]

But the initial cost is what determines whether the first patch will ever be sent, so the amortization may never happen.

[db48x]

I guess technically that’s true, but it cannot possibly take long to learn how to use `git format-patch`, and everyone should already know how to attach a file to an email. Even if you have to spend half an hour reading the entire output of `git format-patch --help`, is that really enough to prevent you from sending your first patch?

[adastra22]

Yes.

[db48x]

Ok, let me get this straight. You diagnosed a problem in the Linux kernel. You debugged it and figured out how to fix it. You edited the kernel source code, recompiled it, and tested your fix. After all that, if you have to read a man page you’ll just give up?

That’s seriously lame.

[adastra22]

What time is more valuable than that, and I don’t owe it to anyone.

[adastra22]

We only have so many hours in our sadly finite lives.