X-Git-Url: https://git.phdru.name/?a=blobdiff_plain;f=pep-git.txt;h=ef0274c4317bb2e7eac473ac07a63260dbfd59a6;hb=30c29e008eb934501f7ee4d2e73a8279f1511988;hp=e0425be37dd93061e77a7da85d9df2c7d15aaaf6;hpb=ebb8083c5e9bbc50f0a37d32d3bf0adb403233c4;p=git-wiki.git diff --git a/pep-git.txt b/pep-git.txt index e0425be..ef0274c 100644 --- a/pep-git.txt +++ b/pep-git.txt @@ -75,12 +75,18 @@ Download and installation Unix users: download and install using your package manager. Microsoft Windows: download `git-for-windows -`_. +`_ or `msysGit +`_. MacOS X: use git installed with `XCode -`_ or download +`_ or download from +`MacPorts `_ or `git-osx-installer -`_. +`_ or +install git with `Homebrew `_: ``brew install git``. + +`Atlassins's SourceTree `_ is a free +Git and Mercurial GUI client for Windows or Mac. Initial configuration --------------------- @@ -101,13 +107,25 @@ Examples of git commands in this PEP use the following approach. It is supposed that you, the user, works with a local repository named ``python`` that has an upstream remote repo named ``origin``. Your local repo has two branches ``v1`` and ``v2``. For most examples the -currently checked out branch is ``v2``. That is, it's assumed you did -something like that:: +currently checked out branch is ``v2``. That is, it's assumed you have +done something like that:: + + $ git clone -b v2 http://git.python.org/python.git + $ cd python + $ git branch v1 origin/v1 + +The last command creates a new local branch v1 and sets +remotes/origin/v1 as its upstream remote branch. + +The same result can achieved with commands:: $ git clone -b v1 http://git.python.org/python.git $ cd python - $ git fetch origin v2:v2 - $ git checkout -b v2 + $ git checkout --track origin/v2 + +The last command creates a new local branch v2, sets +remotes/origin/v2 as its upstream remote branch and checks it out into +the working directory. Branches and branches @@ -146,10 +164,10 @@ To see local and remote branches (and tags) pointing to commits:: $ git log --decorate You never do your own development on remote branches. You create a -local branch that has a remote branch as an upstream and do -development on that local branch. On push git updates remote branches, -and on pull git updates remote branches and fast-forwards, merges or -rebases local branches. +local branch that has a remote branch as upstream and do development +on that local branch. On push git updates remote branches, and on pull +git updates remote branches and fast-forwards, merges or rebases local +branches. When you do an initial clone like this:: @@ -280,7 +298,7 @@ For example:: Git doesn't automatically pushes tags. That allows you to have private tags (lightweight tags are also private for a repo, they cannot be -pushed). To push tag(s) list them explicitly:: +pushed). To push tags list them explicitly:: $ git push origin tag 1.4.2 $ git push origin v1 v2 tag 2.1.7 @@ -325,7 +343,7 @@ safely edit, remove, reorder, combine and split commits that hasn't been pushed yet. You can even push commits to your own (backup) repo, edit them later and force-push edited commits to replace what has already been pushed. Not a problem until commits are in a public -repository. +or shared repository. Undo