Git User's Manual (for version 1.5.3 or newer) - The Diigo Meta page

• 04 Feb 13
  

  Solidus Snk

  Manual de GIT

  git manual referencia programación

• 14 Jan 13
  

  Rokia Lamrani Alaoui

  guide d'utilisation Git

• 15 Nov 12
  

  Roy Y.T. Chen
  • if you have uncommitted changes touching the same files as the ones impacted by the merge, Git will refuse to proceed
  • Most of the time, you will want to commit your changes before you can merge, and if you don’t, then git-stash(1) can take these changes away while you’re doing the merge, and reapply them afterwards.
• 20 Sep 12
  

  Jochen Fromm

  RTFM or TL;DR ? (for version 1.5.3 or newer)

  git manual reference documentation development programming versioncontrol scm

• 01 Jan 12
  

  Gautam Roy

  Coding editor-ide

• 27 Sep 11
  

  florentin s

  git manual

• 06 Sep 11
  

  seanreads

  git scm programming

• 12 Aug 11
  

  dancecodes

  git manual reference documentation scm programming development howto user ! me:icio

• 03 Aug 11
  

  blcham

  git manual

• 15 Jul 11
  

  Ady Gould

  git manual reference documentation scm Version Control Systems - Git #delicious

• 10 Jun 11
  

  Bill Rawlinson

  git tutorial development versioncontrol

• 11 May 11
  

  Laszlo Toth

  git

• 05 May 11
  

  acazsouza

  git reference documentation programming development versioncontrol howto github

• 01 May 11
  

  software documentation programming source control Git

• 28 Apr 11
  

  Bryan M

  github git

• 27 Apr 11
  

  quartzo

  Development documentation git howto manual PROGRAMMING Reference scm Imported from del.icio.us

• 14 Apr 11
  

  Kevin Tomasso

  git user manual

  git

• 02 Apr 11
  

  maddeya

  git dvcs scm tutorial manual reference user-guide

• 26 Mar 11
  

  Ian Scott

  git manual reference documentation programming development versioncontrol

• 03 Mar 11
  

  Marcus Boesch

  github

• 

  Piensa Blogs

  git

• 09 Feb 11
  

  have a git repository to experiment

  git versionskontrolle opensource manual dokumentation referenz

• 30 Jan 11
  

  Sub Proletarian

  git versioncontrol

• 24 Jan 11
  

  Darren Wallace

  software documentation git reference development versioncontrol

• 

  artyom1979

  git manual

• 06 Jan 11
  

  Daniel N

  git reference manual documentation development programming versioncontrol tutorial

• 04 Jan 11
  

  Rafael Soares

  git documentation development versioncontrol howto programming

• 21 Dec 10
  

  a k'wala

  git reference manual documentation scm

• 09 Dec 10
  

  jean-christophe zulian

  git manual reference documentation scm

• 03 Dec 10
  

  alphatesla

  git

• 29 Nov 10
  

  Martin Leyrer

  git

• 

  Rober Morales-Chaparro

  git versions control system tutorial

• 20 Nov 10
  

  pk seet

  Sharing personal repository

  git public repository

• 19 Nov 10
  

  Stéphane Girault

  git

• 17 Nov 10
  

  pradheap

  git reference documentation programming manual

• 30 Oct 10
  

  git

• 28 Oct 10
  

  John Roberts

  git manual reference documentation

• 28 Sep 10
  

  hute37

  git manual reference documentation

• 23 Aug 10
  

  Flavio Copes

  git

• 12 Aug 10
  

  Sébastien Douche

  git

• 31 Jul 10
  

  Kevin Rapley

  git manual howto versioncontrol

• 25 Jul 10
  

  Damien Clark

  git programming development howto

• 24 Jun 10
  

  Filipe Chagas

  git reference manual

• 

  filipeochagas

  git reference manual

• 31 May 10
  

  Doug Hellmann

  git documentation dvcs

• 

  vespertinus

  git

• 

  ger bre

  git manual

• 20 May 10
  

  The Budiman

  Gir User Manual

  tools doc programming

• 14 May 10
  

  philo108

  remove a commit

  git

• 04 May 10
  

  scmoral

  git manual documentation scm

• 29 Apr 10
  

  nao_bear

  git

• 

  fletort

  git manual

• 22 Apr 10
  

  Achim Vedam

  coding git

• 20 Apr 10
  

  fabricioffc

  git

• 18 Apr 10
  

  jameslinder

  git manual documentation docs reference dev

• 14 Apr 10
  

  Shanghao Li

  Git manual collaborative development

  • Git User's Manual (for version 1.5.3 or newer)
• 05 Apr 10
  

  Aiesha Dotson

  git

• 26 Mar 10
  

  Dan O'Neill

  git guide

• 22 Mar 10
  

  John M

  book version_control git linux

• 28 Feb 10
  

  sam scherer
• 24 Feb 10
  

  Soon Cheol
  • Time goes left to right
  • nstead, work may simultaneously proceed along parallel lines of development, called branches,
  • parallel lines of development, called branches,
  • "branch" to mean a line of development, and "branch head" (or just "head") to mean a reference to the most recent commit on a branch.
  • parallel lines of development, called branches,
  • Understanding history: History diagrams
  • create a new branch <new> referencing <start-point>, and  check it out.
  • $ git checkout v2.6.17
  • This is an easy way to check out a particular version without having to make up a name for the new branch. You can still create a new branch (or tag) for this version later if you decide to.
  • $ git branch -r
  • • The branch "test" is short for "refs/heads/test". 
    •  The tag "v2.6.18" is short for "refs/tags/v2.6.18". 
  • origin/master" is short for "refs/remotes/origin/master
  • Updating a repository with git fetch
  • The command "git fetch", with no arguments, will update all of the remote-tracking branches to the latest version found in her repository.

  12 more annotations...

• 23 Feb 10
  

  Paulo Gaspar

  git versioncontrol opensource software manual versioning

• 15 Feb 10
  

  ahrumsong

  git manual

• 14 Feb 10
  

  pvledoux

  git versioning tools

• 04 Feb 10
  

  software development book versioncontrol vcs toread guide programming tools reference tutorial howto linux code opensource kernel documentation version-control scm git distributed dev control version versioning manual doc dvcs docs user delicious import

• 21 Jan 10
  

  Rishav Dixit

  git

• 19 Jan 10
  

  alex perl

  git

• 13 Jan 10
  
• 

  Julian Elve

  git manuals

• 12 Jan 10
  

  giu 123

  git reference

• 11 Jan 10
  

  Scott Blackburn

  git reference version_control

• 

  Marcus Andersson

  git

• 07 Jan 10
  

  git manual reference documentation scm

• 06 Jan 10
  

  A handy user manual for Git.

  git manual reference

• 16 Dec 09
  

  Todd Jobe

  git

• 15 Dec 09
  

  Vera Tkachenko

  git manual

• 01 Dec 09
  

  Pontus Munck

  git documentation

• 19 Nov 09
  

  baustin16

  git reference programming development howto versioncontrol tutorial linux for:dscheuer

• 

  Abhinay Omkar

  manual reference programming development howto tutorial linux tools git scm documentation learn

• 13 Nov 09
  

  Henri-Damien LAURENT

  git reference manual

• 11 Nov 09
  

  Ricardo Olvera

  sci git ops software vcs

• 10 Nov 09
  

  Byju Veedu

  Utilities

• 02 Nov 09
  

  David Fisher

  refspec
  A "refspec" is used by fetch and push to describe the mapping between remote ref and local ref. They are combined with a colon in the format <src>:<dst>, preceded by an optional plus sign, +. For example: git fetch $URL refs/heads/master:refs/

  git

• 05 Oct 09
  

  sjuttiotre

  howto tools software reference linux opensource programming code git versioncontrol

• 04 Oct 09
  

  abologna

  git manual tutorial

• 02 Oct 09
  

  Douglas Muth

  git delicious

• 29 Sep 09
  

  Chris Burbridge

  en version o

  git delicious

• 28 Sep 09
  

  Taras Yagniuk

  Git User Manual (en)

  git source manual documentation

• 23 Sep 09
  

  Damon Snyder

  git reference

• 21 Sep 09
  

  madhavbnk

  git

• 

  Javier Neira

  git reference manual user

  • How to get a git repository
  • Examining branches from a remote repository
  • Getting updates with git pull
  • Git is best thought of as a tool for storing the history of a collection of files. It stores the history as a compressed collection of interrelated snapshots of the project's contents. In git each such version is called a commit.
  • work may simultaneously proceed along parallel lines of development, called branches, which may merge and diverge.
  • It does this by keeping a list of heads which reference the latest commit on each branch;
  • Most projects also use tags. Tags, like heads, are references into the project's history, and can be listed using the git-tag(1) command:
  • The "master" branch that was created at the time you cloned is a copy of the HEAD in the repository that you cloned from. That repository may also have had other branches, though, and your local repository keeps branches which track each of those remote branches, which you can view using the "-r" option to git-branch(1):

  • After you clone a repository and make a few changes of your own, you may wish to check the original repository for updates and merge them into your own work.

    We have already seen how to keep remote tracking branches up to date with git-fetch(1), and how to merge two branches. So you can merge in changes from the original repository's master branch with:

    $ git fetch
     $ git merge origin/master

    However, the git-pull(1) command provides a way to do this in one step:

    $ git pull origin master

    In fact, if you have "master" checked out, then by default "git pull" merges from the HEAD branch of the origin repository. So often you can accomplish the above with just a simple

    $ git pull

  7 more annotations...

• 06 Sep 09
  

  Ryan M

  documentation git versioncontrol programming reference

• 23 Aug 09
  

  Klaus Günther

  search

  git docu wiki

• 20 Aug 09
  

  Bertrand Cachet

  git documentation

• 31 Jul 09
  

  Scott Sanders

  git reference scm documentation manual

• 28 Jul 09
  

  Alberto Ngai

  git manual

• 21 Jul 09
  

  henrique matias

  refs

  manual git scm reference documentation programming development howto

• 16 Jul 09
  

  Dongwook Lee

  git user manual

• 10 Jul 09
  

  Abdul Qabiz

  git user manual reference scm documentation development howto versioncontrol

• 08 Jul 09
  

  jkdirac

  git

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.