I am not a lawyer but according to http://www.copyright.gov/circs/circ01.pdf (See screenshot of relevant section below), mentioning the first year of publication in the copyright is a good thing
Mentioning 2010 as the first release happened at that time - https://github.com/tj/git-extras/releases/tag/0.0.1
Also adding `Contributors` to copyright because TJ Holowaychuk is not the only person owning copyright for the whole project. The copyright is collectively owned by all contributors, or more precisely: every contributor owns a copyright on the code he or she has contributed.
The only way to retain full copyright over code is to ask for signing contributor's agreement before merging in changes. This is, in fact, what some companies who license commercially their free software do.
This was a regression introduced by the useage of `enabledelayedexpansion`,
which results in `!` treated as variable identifier like `%`. The result
was that git didn't treat the scripts as git commands...
User visible:
* Also accept the git install path (and not the mingw64 subdir) as a user
supplied install location. Make it the new default and warn the user if
a mingw64 dir is supplied (=this dir is not checked, so it might be
anywhere...)
* Find git.exe in path and use that as an install location
* Add error|status messages and output less noise (robocopy)
* do some check if column.exe is not found...
* adjust the installation text for windows...
not user visible:
* more.exe does not work when used in a cmd which has a unicode codepage
-> save the current codepage and set a sane default during the install
* do some "magic" with quotes around path variables -> makes it work with
pathes with spaces in it (both final git dir and the git-extra checkout)
* Do not leak variables to the sourounding interpreter
using `-m` or `--merges-only` will only show the merge
commit messages. It will also use the body of the merge
commit message in addition to the subject, as github merges
usually have a useless subject line for commit messages.
If used with `-n/--no-merges`, the last one specified will win.
