summary |
shortlog | log |
commit |
commitdiff |
tree
first ⋅ prev ⋅ next
W. Trevor King [Fri, 29 Nov 2013 22:41:14 +0000 (14:41 -0800)]
COPYING: Add MIT license for this project
The text is from http://opensource.org/licenses/mit-license.html. I
haven't made any local changes yet, so the `<year>` and `<copyright
holders>` markers are still there.
Because I'm not sure I want to use this license yet (maybe I'll use
the BSD license instead?), I've started a new branch for this commit:
$ git checkout -b mit-license master
That creates a new branch `mit-license` based on the current `master`
and checks out the new branch. You can see which branch you're
usually on using `git branch`:
$ git branch
* mit-license
master
The asterix marks the active branch. Once we've checked out the new
branch, creating commits is just like it used to be:
$ git add COPYING
$ git commit
Projects usually include licensing information like this explaining
the terms under which others are allowed to make changes. The file is
often called COPYING or LICENSE. The Open Source Initiative has a
list of popular licenses [1], as does the Free Software Foundation
[2].
[1]: http://opensource.org/licenses/
[2]: http://www.gnu.org/licenses/license-list.html
W. Trevor King [Fri, 29 Nov 2013 22:33:29 +0000 (14:33 -0800)]
README.md: Document the syntax used in the README
Explain that the file is written in Markdown, and link to the Markdown
spec and GitHub's markup parsing docs.
After adjusting README.md in my text editor, I compared my working
directory with the index using:
$ git diff
That looked reasonable, so I committed all the modifications using:
$ git commit --all
The `--all` option tells Git to automatically stage any modifications
or deletions. I could have used the following:
$ git add README.md
$ git commit
and achieved the same result. Some people like to stage changes
explicitly, and some like to stage them automatically. Pick whichever
works best for you.
W. Trevor King [Fri, 29 Nov 2013 22:29:06 +0000 (14:29 -0800)]
README.md: Begin versioning by explaining the project goals
I created this commit by writing README.md in my text exitor. I
staged the file for the next commit with:
$ git add README.md
I committed the staged version of the file with:
$ git commit