A tour of git: the basics - 0 views
-
~ suffix
-
HEAD~
-
HEAD~2" refers to two commits back
- ...19 more annotations...
-
refers to the previous commit
-
$ git log HEAD~3..
-
git show 13ed136b
-
git status" tells us that the current branch is "master"
-
It’s a little bit helpful to know that we’ve modified hello.c, but we might prefer to know exactly what changes we’ve made to it.
-
git diff
-
To set your name and email address, just use the following commands:
-
git config --global user.name "Your Name" git config --global user.email "you@example.com"
-
--author option to the “git commit”
-
a blank line, and then one or more paragraphs with supporting detail. Since many tools only print the first line of a commit message by default, it’s important that the first line stands alone.
-
git commit --amend
-
misspelling in it
-
It's worth emphasizing the value of minimal, independent commits. The smaller the changes are the more useful the history will be when actually using the history, not just viewing it.
-
Just run "git pull" everytime you want to pull in new changes that have landed in the upstream repository.
-
Again, you'll see that this precisely matches the final portion of the output from "git pull". Using "git fetch" and "git merge" let us achieve exactly what "git pull" did, but we were able to stop in the middle to examine the situation, (and we could have decided to reject the changes and not merge them---leaving our master branch unchanged).
-
For now, let's return back to the tip of the master branch by just checking it out again: $ git checkout master
-
$ git --bare init --shared The --shared option sets up the necessary group file permissions so that other users in my group will be able to push into this repository as well.
-
Now, generally the purpose of pushing to a repository is to have some "collaboration point" where potentially multiple people might be pushing or pulling.
-
git clone