Uh, no.
Just use Git. I thought i was sane trying to keep inexperienced teams on Mercurial because of sane command line interfaces and whatnot. Its a losing strategy. Use Git/Github and you'll never be alone in trying to find supporting workflows, tools, documentation or people to help.
I thinks its BS, unless people are factoring in some massive incentives in special case scenarios
At least they have the new code of conduct for the new SJW kernel ready to go
http://sarah.thesharps.us/2015...
Thats from a person that just yesterday claimed 'she is done and out and will stay off the keyboards and internets for a while because feelings'
Trigger warning: your fucking head will likely fucking explode
Most linux users, by far, dont choose their own kernels. They run whatever distro gives them. Or in most cases, whatever is loaded on their phone by the manufacturer
Here is context
https://lkml.org/lkml/2013/7/1...
https://lkml.org/lkml/2013/7/2...
She tried some attention grabbing drama, got all SJWy, was briefly shot down, butthurt feelings etc. Now she quit
Factor in Musk time dilation factor. When he says 2017, you have to be pretty precise about the gravitational lensing his ego has created in the room that particular day. It's normally around 2071 or so
Overall seems like a pretty decent device given the price
The summary failed to give the price. Google says $379 5X, and $499 for 6P ( i dont care about subsidized prices )
You'll really actually want President Camacho
'Dry foods' is bollocks. You can order 'fresh food and groceries' from Google Express right now
Um i have seen Google Express cars around here for years now, presumably doing mostly grocery deliveries. Not sure what we are talking about ?
The other thing is to hack your build of the toolchain, so that __TIME__ and __DATE__ and __FILE__ could be stubbed and/or overridden by command line. Havent looked at GCC or clang codebases, but i would think it wouldnt be too hard.
__FILE__ has a similar effect, as it refers to absolute path. Absolute build paths would also be have to be created deterministically, no temp directories or anything like that. And then, make sure everything that gets linked in statically, including the toolchain bits follow the same rules.
Unless you freeze system time for the full duration of the build, every piece of code that builds in __TIME__ or __DATE__ macros, will screw with this. Other environment macros injected into the build ( like git revision etc ) as well.
There is a package manager. https://chocolatey.org/
No, i wasn't saying its going to help you or anyone else. What i was saying is that at the abstract level, its simply a local optimization vs global optimization issue.
Whether this optimization is feasible or can work for any given problem with any given implementation is a different matter altogether.
An unconnected device/thing can at best perform local optimization because it simply does not have larger context and information, global optimization cannot be performed.
"The Mets were great in 'sixty eight, The Cards were fine in 'sixty nine, But the Cubs will be heavenly in nineteen and seventy." -- Ernie Banks
