Best content in interesting_sites

Verbs: arrange, define, duplicate, label, list, memorize, name, order, recognize, relate, recall, repeat, reproduce state.
...

Cancel
Verbs: classify, describe, discuss, explain, express, identify, indicate, locate, recognize, report, restate, review, select, translate.
...

Cancel
Verbs: apply, choose, demonstrate, dramatize, employ, illustrate, interpret, operate, practice, schedule, sketch, solve, use, write.
...

Cancel
...3 more annotations...
Verbs: analyze, appraise, calculate, categorize, compare, contrast, criticize, differentiate, discriminate, distinguish, examine, experiment, question, test.
...

Cancel
Verbs: arrange, assemble, collect, compose, construct, create, design, develop, formulate, manage, organize, plan, prepare, propose, set up, write.
...

Cancel
Verbs: appraise, argue, assess, attach, choose compare, defend estimate, judge, predict, rate, core, select, support, value, evaluate.
...

Cancel

A tour of git: the basics - 0 views

cworth.org/tour

git tutorial

shared by pagetribe . on 19 Feb 09 - Cached

~ suffix
...

Cancel
HEAD~
...

Cancel
HEAD~2" refers to two commits back
...

Cancel
...19 more annotations...
refers to the previous commit
...

Cancel
$ git log HEAD~3..
...

Cancel
git show 13ed136b
...

Cancel
git status" tells us that the current branch is "master"
...

Cancel
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.
...

Cancel
git diff
...

Cancel
To set your name and email address, just use the following commands:
...

Cancel
git config --global user.name "Your Name" git config --global user.email "you@example.com"
...

Cancel
--author option to the “git commit”
...

Cancel
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.
...

Cancel
git commit --amend
...

Cancel
misspelling in it
...

Cancel
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.
...

Cancel
Just run "git pull" everytime you want to pull in new changes that have landed in the upstream repository.
...

Cancel
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).
...

Cancel
For now, let's return back to the tip of the master branch by just checking it out again: $ git checkout master
...

Cancel
$ 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.
...

Cancel
Now, generally the purpose of pushing to a repository is to have some "collaboration point" where potentially multiple people might be pushing or pulling.
...

Cancel
git clone
...

Cancel