It means less than 50% of votes were cast for him. In simpler terms, more people voted for someone else than him.
Michal
If the files were already staged then git should have blobs in the git folder, so they should be recoverable.
In the context of version control it does. Discarding a change that creates a file means deleting the file.
Bit over 2 weeks but doable
TIL I'm a chick magnet
Calico by Lee Goldberg
How do you like it? I started the first book a couple weeks ago but just couldn't finish. Sci fi isn't really my thing, although i did like John Scalzi's books.
'The first Fifteen Lives of Harry August' was pretty good.
Besides that, 'The Waiting' by Michael Connelly, but he's my favorite author, so I'll recommend almost each of his books.
I believe the distinction is you have a right to copy for own use/backup but you don't have the right to break the DRM preventing you from doing so.
For example, you have a right to make a copy of a video game (by installing it to hard drive) but DRM willl prevent you from running it unless you have the original disk in the drive.
Requirements are literally the packages your project requires to run,down to a specific version if you wish.
Constraints specifies what version of a package to install IF the package is required by your requirements, or by transitive requirement (required by packages you require). If package is not required, the constraint is not used.
I tend to use requirements file to list direct dependencies of my project and their versions. Constraints is useful to pin down and transitive dependencies to make sure they're not accidentally upgraded (repeatable builds) . Also if the 3rd party package drops a requirement you don't have to worry that it'll still be installed if it's still on your constraints. It'll simply not be installed.