And here it is in the kernel contribution documentation.
Simple example:
- bad:
Added foo interface. - good: Add foo interface.
So the commit says what applying the patch will do, not what you worked on.
And here it is in the kernel contribution documentation.
Simple example:
So the commit says what applying the patch will do, not what you worked on.
I feel like I’m reading a different article than everyone else. The comments made me think the article would be adding advertisements, but it seems to be trying to find a way forward to facilitate advertisements while maintaining privacy.
Without technical details I’m not sure that’s a bad thing. I know lemmy is largely “Mozilla bad”, but I’m just not sure the comments are in line with the proposal.
No I’m Spartacus.
It really forks the llamas ass!
Can we get a version with all treehouses?
Fortunately, they aren’t being asked to do that. All the rust team was requesting was metadata about the call signatures so that they could have a grasp on expected behavior.
A bunch of people that either failed to understand the value of the moderation system or are just crybabies about being expected to follow the rules answering here.
It is easy to use and not nearly as toxic as most of the internet will claim. Research your question, ask clearly, include the code you attempted for a minimal reproduction, and include debugging details. If you don’t do those things, you are the problem, not the people closing your questions.
I use it often per month.
It looks well designed. I wonder if it will find purchase among users.
Like all other patterns, it can be done well or done poorly. I’ve experienced both with monorepos. The pain is greater when it is painful. But if the contribution, build, and release procedures are well designed and clearly documented it can also be nice.
Most call it the Old Testament, and not quite. The Old Testament is a superset of the Torah. But contains many books that aren’t part of the Torah.
Yeah it cuts both ways though. First I am generalizing. Some indeed have proclivities, but I’m saying you shouldn’t just assume it is easy for them. A lot of improvement is based on effort. Not all, but it is similarly frustrating to have people diminish successes as luck or “talent”.
Agreed. I should have been more clear. They’ve put in more effort. Either by working harder (short time) or working more over a long period. I just see a lot of people think things comes naturally to others, but not really. One may have a proclivity for something, but it still takes time to cultivate a skill.
Additionally, just because something hard for you looks like it comes easily to another, it probably doesn’t. They’re just working harder.
This indicative mood is something I would send back for correction or correct myself where I am the maintainer. However I understand that although this is pretty consistent through FOSS, it is not a settled matter especially in corpo-land. Most important is that it is consistent within a project. See many differing views here on Stackoverflow, noting the most popular answer though is imperative as Linus requests.