Readit NewsIt's a common noun which works really well for patch-based offerings I guess, and we chose it because we built a 'framework to patch code'. But we'll think more about this - thanks for bringing it up.
When I saw your submission title I thought it was that Patchwork.
https://earthquake.usgs.gov/earthquakes/map/?currentFeatureI...
The Belden quake is 4.4 at 7.8 km, and 4.2 at 5 km.
It's a log scale so the Whitehouse quake is much larger, but the significance of the quake seems to be more than just these numbers because Belden quake is irrelevant (didn't make the news really).
Sarupathar was a 5.8 (huge comparatively) at 10 km. Hualien was 5.1 at 15.9 km and talked about more than Sarupathar. So the defining aspect appears to be how many people are within range of the epicenter rather than just raw depth and magnitude. Which makes sense, I suppose. We care about how population centers encounter the movement!
That's just an aftershock.
The main quake was three days ago. M 7.4 according to USGS: https://earthquake.usgs.gov/earthquakes/eventpage/us7000m9g4...
So for an earthquake that's almost 1000x as strong, you'd think it'd be talked about more.
Or if you set rootfstype=ramfs, then you can take up to all of physical RAM, but ramfs isn't swappable.
To be 100% sure that something hasn't changed recently I tried and, nope, your revision command only looks at the local reflog, after a forced push you get different answers from the original repository (that has the full reflog) and a new clone.
That the developer is not aware that their diagnostic raises a red flag itself raises a red flag. It doesn't occur to them that a system which issues this diagnostic will be suspected of doing stupid things. That tends to betray a lack of sophistication in the area of security.
The good thing about passwords is that it just depend on your mind. You can travel through any country with hostile customs with empty pockets. No one can get your "authentication device" and there is not even a proof that you have an account on any website. Or that you don't have multiple of them.
> Incremental ZFS send streams do not have any of these properties and full ZFS send streams only have a few of them. Neither full nor incremental streams have any resilience against damage to the stream; a stream is either entirely intact or it's useless. Neither has selective restores or readily available indexes. Incremental streams are completely useless without everything they're based on. All of these issues will sooner or later cause you pain if you use ZFS streams as a backup format.
https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSSendNotA...