HN user

auscompgeek

443 karma

A random computer geek on the internet. Comments are CC BY-ND 4.0.

[ my public key: https://keybase.io/auscompgeek; my proof: https://keybase.io/auscompgeek/sigs/YAPgKToNiXmJT9OPvUBCgnFlUWG1GFWt8UGTOzBEXRw ]

Posts7
Comments165
View on HN

describe is also the command you can use to edit the commit message of the change you're currently drafting. In jj there's no staging area, every modification to the working tree immediately gets integrated into the current commit. (This means if you have no diff in your working tree, you're actually on an empty commit.)

I would've considered signing up if scrolling on your website didn't make my modern flagship phone drop frames.

Indeed, while Chrome is displaying the dialog, it blocks all Chrome extension popup windows from appearing.

We discovered this one the hard way at work. I keep learning this the hard way myself because I've been working on browser extension dev lately. I don't understand how this could possibly be an intended feature.

I wanted to check this out, so I installed the GitHub app on my account, with access to all my personal repos. However when I went looking for one of my repos (auscompgeek/sphinxify) I couldn't find it. It looks like I can only see the first 100 repos in the dashboard? I have a lot of forks under my account…

They can't block every 8 character tag.

Whilst Git will be default abbreviate commits to 7 characters, that's merely a default; `core.abbrev` can be set to any number to change the default display. Git will also accept any length abbreviated hashes as long as they're unique in the repo.

The ChromiumOS Python style guide notes the difference between Google's public Python style guide and their internal one.

New projects should use that unmodified public Python Google style guide (4 space indent with methods_with_underscores). Historically, we adopted a style that was congruent with Google internal Python style guide (2 spaces with MethodsAsCamelCase).

https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sty...

DNSSEC adoption is pretty low outside of customers of large nameserver providers (that support DNSSEC out of the box), and also requires the registrar and registry support DNSSEC too. Unfortunately there are still some out there that don't.