Notices by muesli (fribbledom@mastodon.social), page 37

@clarjon1

Highly recommended! It certainly improves your code quality, too. Can't count anymore how many times that has saved me from committing some utter nonsense I may not have discovered for a long time otherwise.

@palecur

@palecur

😂

@clarjon1

In that case you may as well use "git commit -a" which essentially does "git add *" for you.

"git add -p" makes you and lets you confirm each individual change hunk before staging it. This also means you can add only some changes within a file and leave other changes for a later commit.

@palecur

@Rosemary

Stages and commits any and all files that have been modified or deleted.

@palecur

That's fine if it's your own little code base, but as soon as you're working with (even just a small) team, this quickly becomes unmaintainable or -reviewable.

"git commit -a" is what I call a cowboy-commit, and I still think git should flag and expose commits as such.

Not that I mind anyone using it (carefully), but it would make me extra wary when reviewing a commit. It should be the absolute exception, not the standard way of committing things.

Do it properly and always review your individual changes once more! Use "git add -p"!

You will soon love it and whoever reviews your code will love you for using it!

@syntaktis

The scheme and domain are the only parts of a URL that are case-insensitive. See RFC 3986.

@ezfe

No need to apologize, I never feel bothered to respond to sensible, intelligent questions!

It also clearly isn't super obvious this would lead to issues, which is why Microsoft probably ended up in this situation to begin with.

@ezfe

Just a few examples:

Many projects link their GitHub namespace with other services like CIs, Linters, Test Badges, Doc Generators and so on. They usually treat URLs case-sensitively, which now leads to broken references. Try to click the build badge on one of their own projects, and see where it takes you: https://github.com/microsoft/vscode-go

Some build systems will fail as they check out dependencies including the full canonical namespace, and now can't find the uppercase version in the filesystem.

@ezfe

That's part of the problem, as it still changes the canonical name of everything within that namespace: build systems, caches, image references and a bunch of other things will break - as they treat URLs case-sensitively as various RFCs and the W3C suggest.

I guess Microsoft is just learning that lesson now.

@eater

I'm not sure breaking W3C's standards and various RFCs (3986 as one example) is something I'd call a feature.

Besides that, it's ignoring the case-sensitivity handling git itself imposes, the very tool it builds upon. Keep calling it what you want, it leads to real-world problems and that's what I call a bug.

@eater

That's great for GitHub, but it still breaks build systems, imports, caches, image links and other references, because they are now pointing to a different canonical name.

Example?

Some of their own repositories use external services, like TravisCI, which now have broken links & references.

Try to click the build badge on https://github.com/microsoft/vscode-go and see where it takes you.

Microsoft apparently still doesn't quite understand the concept of case-sensitivity in filenames & URLs and just changed github.com/Microsoft to github.com/microsoft, in turn breaking a ton of canonical URLs and references.

It's incredible how shortsighted and oblivious a company of that size can be, really 🙄

https://twitter.com/mschoening/status/1125521372828934144

@thomasfuchs

Childhood memories... err, or rather phantasies! I remember how much I wanted these kits and how stupidly expensive they were.

You should probably open a tech museum at some point in your life 😆

@snder

So good, indeed!

@thomasfuchs

Or as I call it: purr programming.

Furious rainbow unicorn is furious!

@michelamarie

I agree, hence why I wrote service-monitor 😉 We simply didn't have nice APIs to filter logs by level and other criteria before. Or to monitor a service's state.

@claudiom

@nik

I like the way you're thinking! 😊

@jasper

Yeah, it's pretty undiscoverable as a user, I'd say.

The first command probably works, too. It's not supposed to output something, it just sends a UDP message to your localhost, port 1337.

@nik