X-Git-Url: https://git.phdru.name/?a=blobdiff_plain;f=pep-git.txt;h=2b55d6341cc55f7a9ceb87e9010ef0d680d97c18;hb=5951ed5068761231f74d262aaa9a8a290a3fae99;hp=118fc87a32b5a8b50de1b7ddf1f44c8c9eb2ab60;hpb=afd0c6a745a6364a545abb8a72a767a78c4ed694;p=git-wiki.git diff --git a/pep-git.txt b/pep-git.txt index 118fc87..2b55d63 100644 --- a/pep-git.txt +++ b/pep-git.txt @@ -75,20 +75,30 @@ 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``. + +`git-cola `_ is a sleek and +powerful Git GUI written in Python and GPL licensed. Linux, Windows, +MacOS X. + +`TortoiseGit `_ is a Windows Shell Interface +to Git based on TortoiseSVN; open source. Initial configuration --------------------- This simple code is often appears in documentation, but it is -important so let repeat it here. Git marks every commit with author -and committer names/emails, so configure your real name and preferred -email:: +important so let repeat it here. Git stores author and committer +names/emails in every commit, so configure your real name and +preferred email:: $ git config --global user.name "User Name" $ git config --global user.email user.name@example.org @@ -104,10 +114,22 @@ local repo has two branches ``v1`` and ``v2``. For most examples the 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 @@ -156,8 +178,9 @@ When you do an initial clone like this:: $ git clone -b v1 http://git.python.org/python.git git clones remote repository ``http://git.python.org/python.git`` to -directory ``python``, creates remote branches and checks out branch -``v1`` into the working directory. +directory ``python``, creates remote branches, creates a local branch +``v1``, configure it to track upstream remotes/origin/v1 branch and +checks out ``v1`` into the working directory. Updating local and remote branches ---------------------------------- @@ -207,6 +230,20 @@ that non-current branch and then merge:: # rebase instead of merge $ git merge v1 +If you have not yet pushed commits on ``v1``, though, the scenario has +to become a bit more complex. Git refuses to update +non-fast-forwardable branch, and you don't want to do force-pull +because that would remove your non-pushed commits and you would need +to recover. So you want to rebase ``v1`` but you cannot rebase +non-current branch. Hence, checkout ``v1`` and rebase it before +merging:: + + $ git checkout v1 + $ git pull --rebase origin v1 + $ git checkout v2 + $ git pull --rebase origin v2 + $ git merge v1 + It is possible to configure git to make it fetch/pull a few branches or all branches at once, so you can simply run @@ -264,6 +301,12 @@ non-bare repository: git refuses to update remote working directory. You really should push only to bare repositories. For non-bare repositories git prefers pull-based workflow. +When you want to deploy code on a remote host and can only use push +(because your workstation is behind a firewall and you cannot pull +from it) you do that in two steps using two repositories: you push +from the workstation to a bare repo on the remote host, ssh to the +remote host and pull from the bare repo to a non-bare deployment repo. + Tags '''' @@ -272,7 +315,7 @@ during fetch/pull. To fetch all tags (and commits they point to) run ``git fetch --tags origin``. To fetch some specific tags fetch them explicitly:: - $ git fetch origin tag NAME1 tag NAME2... + $ git fetch origin tag TAG1 tag TAG2... For example:: @@ -280,11 +323,13 @@ 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 +Don't move tags with ``git tag -f`` after they have been published. + Commit editing and caveats ========================== @@ -338,22 +383,58 @@ How to undo a merge https://kernel.org/pub/software/scm/git/docs/howto/revert-a-faulty-merge.html -Advanced topics -=============== +Merge or rebase? +================ -Staging area ------------- +Internet is full of heated discussions on the topic: "merge or +rebase?" Most of them are meaningless. When a DVCS is being used in a +big team with a big and complex project with many branches there is +simply no way to avoid merges. So the question diminished to "whether +to use rebase, and if yes - when to use rebase?" Considering that it +is very much recommended not to rebase published commits the question +diminished even further: "whether to use rebase on non-pushed +commits?" -Staging area aka index is a distinguishing feature of git. See -`WhatIsTheIndex -`_ and -`IndexCommandQuickref -`_ in Git -Wiki. +That small question is for the team to decide. The author of the PEP +recommends to use rebase when pulling, i.e. always do ``git pull +--rebase`` or even configure automatic setup of rebase for every new +branch:: + $ git config branch.autosetuprebase true -Merge or rebase? -================ +and configure rebase for existing branches:: + + $ git config branch.NAME.rebase true + +After that ``git pull origin v2`` will be equivalent to ``git pull +--rebase origin v2``. + +In case when merge is preferred it is recommended to create new +commits in a separate feature or topic branch while using rebase to +update the mainline branch. When the topic branch is ready merge it +into mainline. To avoid a tedious task of resolving conflicts you can +merge the topic branch to the mainline from time to time and switch +back to the topic branch to continue working on it. The entire +workflow would be something like:: + + $ git checkout -b issue-42 # create and switch to a new branch + ...edit/test/commit... + $ git checkout v2 + $ git pull --rebase origin v2 # update v2 from the upstream + $ git merge issue-42 + $ git branch -d issue-42 # delete the topic branch + $ git push origin v2 + +When the topic branch is deleted only the label is removed, commits +are stayed in the database, they are now merged into v2:: + + --o--o--o--o--o--o-M-`_ and +`IndexCommandQuickref +`_ in Git +Wiki. + + Advanced configuration ====================== @@ -391,9 +486,17 @@ TODO: dangling objects, git gc, git repack. Tips and tricks =============== +TODO: sticky options; example: git grep -O. + TODO: bash/zsh completion, bash/zsh prompt. +git on server +============= + +TODO: anonymous access; git over ssh; gitolite; gitweb; cgit; gitlab. + + From Mercurial to git =====================