.git-blame-ignore-revs, while great, unfortunately belongs in the “Other Conventions” section.

If you configure your git client to use it, git blame will fail in any repository in which one is not present.

As of git 2.52, it's possible to use (:optional) to avoid errors in repositories that don't have this file https://stackoverflow.com/a/79824780

!! Thank you!

It appears to be in the fourth paragraph.

https://www.fda.gov/medical-devices/medical-device-recalls-a...

> As of November 14, 2025, Abbott has reported 736 serious injuries, and seven deaths associated with this issue.

I had always wondered if that happened because of a proliferation in folks named EionMusk.

tar.exe, however, beats both of those in terms of archive format support and speed.

It comes with Windows, and has since 2022! Alas, if you mean Windows 10 then you can use some DISM magic to add it to an install image.

The author of the post indicated that they are releasing an update to an existing game, which we can presume has the same executable filename.

I’ve noticed most of the replies to your comment address the first half, and none (as of right now) address the second:

> So the question that comes to my mind is whether this is yet further new and different Raspberry Pi 5 hardware that comes with no software or prospect of software.

If by “this” you mean the MicroSD Express hat from the article: this is a hobby project produced by a hobbyist, who seems to have no plans to sell or mass produce it.

It is unfair to the creator for you to lump it in with, and draw a conclusion from, the works produced by Raspberry Pi Holdings.

If you can turn the port off and then back on remotely, perhaps you can skip the unplugging part completely? I know that some managed PoE switches even offer a button to power cycle a port.

Good point, now that you mention it, it's not turning off PoE, just stopping data. I don't know if there's a great way to handle it, and there's no way I'm shutting off the entire switch. I'll just unplug the patch panel end of the cable, instead of the switch end, so the jack I'm wearing out is one that's easy to replace.

It's just the chip the NSA put in the cable, failing to initialize first try.

Have you come by your certainty that they have not asked because you were a contributor?

The advice in the 2014 talk applies to exporting specific types of errors as part of a package’s public API surface.

The article, on the other hand, advocates for local variables storing errors not to have distinct names.

So a public variable error should follow different naming conventions then a local variable? That doesn't seem right, the go wiki says you should use the 'err' prefix for both (capitalized for public variables though, obviously)

And I'm only asking about when you are giving an error a distinct name, not just naming it 'err'.