With a recent stable or longterm kernel it's simply mitigations=off.
Oh no, I got the title wrong! Yes, of course I remember what it is about. And, yes, it is perfectly applicable here.
You may well be right. I probably only notice it with software because that's what I do every day.
Is it also gatekeeping to say that emacs is for programmers? What about C++? I don't keep any gates. Please come in and learn how to program. I love it and you might do too. But just understand that git is through this…
Subversion. Or some special purpose versioning system like "track changes".
Unfortunately this article, like almost all others, is still wrong because it looks like commits get mutated when you rebase and the old commits disappear. It is very important to understand that commits (in fact, all…
That's because a file system is something you already understand, even if you've never actually used an old fashioned paper filing system. The software is providing you with something you understand. Git is not…
Git is just for programmers. It was made by and for kernel developers, no less. There are better tools for other people. If you don't care what a DAG is, you will never understand what git is or what it's for. No…
You're actually getting at something deeper which I've been noticing more and more lately. Many people seem really reluctant to learn how to use things. It only seems to happen with software. They see a program or a new…
Git is not hard. It's very simple. But people learn it the wrong way. You have to learn it from the DAG up. If you cannot grasp how the DAG works you'll forever be reading and writing articles like this one which do not…
I refer you to the children's story "Crying Wolf".
I actually thought the flag code disallowed flying the flag in bad weather. But I'm now unable to find any confirmation of that.
The continual broadening of the definition of rape will only dampen its impact and harm the few genuine victims of rape.
It can contain a link to the list of all invoices. So you could have /customer/<cid>/invoice which lists all invoices for the customer which are actually just links of the form /customer/<cid>/invoice/<iid>
Is that based on the size of the vehicle? In my country it is not. It is only based on emissions. Some SUVs will pay less tax than a small sports car.
You gained the ability to find the invoice. There is no need to have customer id in the invoice url. Just /invoice/invoice_id is enough.
> When it storms and gets wet, it’s all I can hear inside my house. Isn't that illegal?
I agree but I'd also like to see tax paid on size of the vehicle because it's literally using more of the public highway. So motorbikes would still pay less, probably. The SUV users say it improves safety. OK, they can…
There shouldn't be separate endpoints that take an owner's ID. That's bad design. The owner endpoint should contain a list of invoices, ie. links to the invoice endpoint.
Indeed. Hyperlinked serialisers are built in and super easy to use. And it makes so much sense when you use DRF's API browser too.
Why does every docker image build have to pull the packages? Are you force rebuilding and defeating docker's cache mechanism?
As usual it will take a disaster for people to realise it was a bad idea. Microsoft tried to destroy Linux in the past. Literally. Linux is what gave us git in the first place, and docker, and so much technology that we…
All of these advantages don't make sense if half your commits are broken versions of the software. Rebasing helps ensure that each commit is valid. That's important for the reasons you mention. Having a log of what you…
I'm not talking about squashing the feature branch. I'm talking about squashing all of master down to one commit (initial commit). If you don't take care of your history, my question is why do you keep it at all?
What do you use your git history for? History is either worth keeping, in which case you should maintain it like any other artifact, or it's not, in which case you should squash down master to a single commit every time…
With a recent stable or longterm kernel it's simply mitigations=off.
Oh no, I got the title wrong! Yes, of course I remember what it is about. And, yes, it is perfectly applicable here.
You may well be right. I probably only notice it with software because that's what I do every day.
Is it also gatekeeping to say that emacs is for programmers? What about C++? I don't keep any gates. Please come in and learn how to program. I love it and you might do too. But just understand that git is through this…
Subversion. Or some special purpose versioning system like "track changes".
Unfortunately this article, like almost all others, is still wrong because it looks like commits get mutated when you rebase and the old commits disappear. It is very important to understand that commits (in fact, all…
That's because a file system is something you already understand, even if you've never actually used an old fashioned paper filing system. The software is providing you with something you understand. Git is not…
Git is just for programmers. It was made by and for kernel developers, no less. There are better tools for other people. If you don't care what a DAG is, you will never understand what git is or what it's for. No…
You're actually getting at something deeper which I've been noticing more and more lately. Many people seem really reluctant to learn how to use things. It only seems to happen with software. They see a program or a new…
Git is not hard. It's very simple. But people learn it the wrong way. You have to learn it from the DAG up. If you cannot grasp how the DAG works you'll forever be reading and writing articles like this one which do not…
I refer you to the children's story "Crying Wolf".
I actually thought the flag code disallowed flying the flag in bad weather. But I'm now unable to find any confirmation of that.
The continual broadening of the definition of rape will only dampen its impact and harm the few genuine victims of rape.
It can contain a link to the list of all invoices. So you could have /customer/<cid>/invoice which lists all invoices for the customer which are actually just links of the form /customer/<cid>/invoice/<iid>
Is that based on the size of the vehicle? In my country it is not. It is only based on emissions. Some SUVs will pay less tax than a small sports car.
You gained the ability to find the invoice. There is no need to have customer id in the invoice url. Just /invoice/invoice_id is enough.
> When it storms and gets wet, it’s all I can hear inside my house. Isn't that illegal?
I agree but I'd also like to see tax paid on size of the vehicle because it's literally using more of the public highway. So motorbikes would still pay less, probably. The SUV users say it improves safety. OK, they can…
There shouldn't be separate endpoints that take an owner's ID. That's bad design. The owner endpoint should contain a list of invoices, ie. links to the invoice endpoint.
Indeed. Hyperlinked serialisers are built in and super easy to use. And it makes so much sense when you use DRF's API browser too.
Why does every docker image build have to pull the packages? Are you force rebuilding and defeating docker's cache mechanism?
As usual it will take a disaster for people to realise it was a bad idea. Microsoft tried to destroy Linux in the past. Literally. Linux is what gave us git in the first place, and docker, and so much technology that we…
All of these advantages don't make sense if half your commits are broken versions of the software. Rebasing helps ensure that each commit is valid. That's important for the reasons you mention. Having a log of what you…
I'm not talking about squashing the feature branch. I'm talking about squashing all of master down to one commit (initial commit). If you don't take care of your history, my question is why do you keep it at all?
What do you use your git history for? History is either worth keeping, in which case you should maintain it like any other artifact, or it's not, in which case you should squash down master to a single commit every time…