giteveryday(7)

—

Options · 1

1.	update hook howto

NAME

giteveryday - A useful minimum set of commands for Everyday Git

DESCRIPTION

Git users can broadly be grouped into four categories for the purposes of describing here a small set of useful commands for everyday Git.

INDIVIDUAL DEVELOPER (STANDALONE)

A standalone individual developer does not exchange patches with other people, and works alone in a single repository, using the following commands.

Examples

Use a tarball as a starting point for a new repository.

bash

$ tar zxf frotz.tar.gz
$ cd frotz
$ git init
$ git add . \n(1)\n
$ git commit -m "import of frotz source tree."
$ git tag v2.43 \n(2)

1.	add everything under the current directory.
2.	make a lightweight, unannotated tag.

Create a topic branch and develop.

bash

$ git switch -c alsa-audio \n(1)\n
$ edit/compile/test
$ git restore curses/ux_audio_oss.c \n(2)\n
$ git add curses/ux_audio_alsa.c \n(3)\n
$ edit/compile/test
$ git diff HEAD \n(4)\n
$ git commit -a -s \n(5)\n
$ edit/compile/test
$ git diff HEAD^ \n(6)\n
$ git commit -a --amend \n(7)\n
$ git switch master \n(8)\n
$ git merge alsa-audio \n(9)\n
$ git log --since='3 days ago' \n(10)\n
$ git log v2.43.. curses/ \n(11)

1.	create a new topic branch.
2.	revert your botched changes in curses/ux_audio_oss.c .
3.	you need to tell Git if you added a new file; removal and modification will be caught if you do git commit -a later.
4.	to see what changes you are committing.
5.	commit everything, as you have tested, with your sign-off.
6.	look at all your changes including the previous commit.
7.	amend the previous commit, adding all your new changes, using your original message.
8.	switch to the master branch.
9.	merge a topic branch into your master branch.
10.	review commit logs; other forms to limit output can be combined and include -10 (to show up to 10 commits), --until=2005-12-10 , etc.
11.	view only the changes that touch what’s in curses/ directory, since v2.43 tag.

INDIVIDUAL DEVELOPER (PARTICIPANT)

A developer working as a participant in a group project needs to learn how to communicate with others, and uses these commands in addition to the ones needed by a standalone developer.

Examples

Clone the upstream and work on it. Feed changes to upstream.

bash

$ git clone git://git.kernel.org/pub/scm/.../torvalds/linux-2.6 my2.6
$ cd my2.6
$ git switch -c mine master \n(1)\n
$ edit/compile/test; git commit -a -s \n(2)\n
$ git format-patch master \n(3)\n
$ git send-email --to="person <[email protected]>" 00*.patch \n(4)\n
$ git switch master \n(5)\n
$ git pull \n(6)\n
$ git log -p ORIG_HEAD.. arch/i386 include/asm-i386 \n(7)\n
$ git ls-remote --heads http://git.kernel.org/.../jgarzik/libata-dev.git \n(8)\n
$ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL \n(9)\n
$ git reset --hard ORIG_HEAD \n(10)\n
$ git gc \n(11)

1.	checkout a new branch mine from master.
2.	repeat as needed.
3.	extract patches from your branch, relative to master,
4.	and email them.
5.	return to master , ready to see what’s new
6.	git pull fetches from origin by default and merges into the current branch.
7.	immediately after pulling, look at the changes done upstream since last time we checked, only in the area we are interested in.
8.	check the branch names in an external repository (if not known).
9.	fetch from a specific branch ALL from a specific repository and merge it.
10.	revert the pull.
11.	garbage collect leftover objects from reverted pull.

Push into another repository.

bash

satellite$ git clone mothership:frotz frotz \n(1)\n
satellite$ cd frotz
satellite$ git config --get-regexp '^(remote|branch)\.' \n(2)\n
remote.origin.url mothership:frotz
remote.origin.fetch refs/heads/*:refs/remotes/origin/*
branch.master.remote origin
branch.master.merge refs/heads/master
satellite$ git config remote.origin.push \
\n
           +refs/heads/*:refs/remotes/satellite/* \n(3)\n
satellite$ edit/compile/test/commit
satellite$ git push origin \n(4)\n
mothership$ cd frotz
mothership$ git switch master
mothership$ git merge satellite/master \n(5)

1.	mothership machine has a frotz repository under your home directory; clone from it to start a repository on the satellite machine.
2.	clone sets these configuration variables by default. It arranges git pull to fetch and store the branches of mothership machine to local remotes/origin/* remote-tracking branches.
3.	arrange git push to push all local branches to their corresponding branch of the mothership machine.
4.	push will stash all our work away on remotes/satellite/* remote-tracking branches on the mothership machine. You could use this as a back-up method. Likewise, you can pretend that mothership "fetched" from you (useful when access is one sided).
5.	on mothership machine, merge the work done on the satellite machine into the master branch.

Branch off of a specific tag.

bash

$ git switch -c private2.6.14 v2.6.14 \n(1)\n
$ edit/compile/test; git commit -a
$ git checkout master
$ git cherry-pick v2.6.14..private2.6.14 \n(2)

1.	create a private branch based on a well known (but somewhat behind) tag.
2.	forward port all changes in private2.6.14 branch to master branch without a formal "merging". Or longhand git format-patch -k -m --stdout v2.6.14..private2.6.14 \| git am -3 -k

An alternate participant submission mechanism is using the git request-pull or pull-request mechanisms (e.g. as used on GitHub (www.github.com) to notify your upstream of your contribution.

A fairly central person acting as the integrator in a group project receives changes made by others, reviews and integrates them and publishes the result for others to use, using these commands in addition to the ones needed by participants.

This section can also be used by those who respond to git request-pull or pull-request on GitHub (www.github.com) to integrate the work of others into their history. A sub-area lieutenant for a repository will act both as a participant and as an integrator.

Examples

A typical integrator’s Git day.

bash

$ git status \n(1)\n
$ git branch --no-merged master \n(2)\n
$ mailx \n(3)\n
& s 2 3 4 5 ./+to-apply
& s 7 8 ./+hold-linus
& q
$ git switch -c topic/one master
$ git am -3 -i -s ./+to-apply \n(4)\n
$ compile/test
$ git switch -c hold/linus && git am -3 -i -s ./+hold-linus \n(5)\n
$ git switch topic/one && git rebase master \n(6)\n
$ git switch -C seen next \n(7)\n
$ git merge topic/one topic/two && git merge hold/linus \n(8)\n
$ git switch maint
$ git cherry-pick master~4 \n(9)\n
$ compile/test
$ git tag -s -m "GIT 0.99.9x" v0.99.9x \n(10)\n
$ git fetch ko && for branch in master maint next seen \n(11)\n
\n
    do
\n
        git show-branch ko/$branch $branch \n(12)\n
\n
    done
$ git push --follow-tags ko \n(13)

1.	see what you were in the middle of doing, if anything.
2.	see which branches haven’t been merged into master yet. Likewise for any other integration branches e.g. maint , next and seen .
3.	read mails, save ones that are applicable, and save others that are not quite ready (other mail readers are available).
4.	apply them, interactively, with your sign-offs.
5.	create topic branch as needed and apply, again with sign-offs.
6.	rebase internal topic branch that has not been merged to the master or exposed as a part of a stable branch.
7.	restart seen every time from the next.
8.	and bundle topic branches still cooking.
9.	backport a critical fix.
10.	create a signed tag.
11.	make sure master was not accidentally rewound beyond that already pushed out.
12.	In the output from git show-branch , master should have everything ko/master has, and next should have everything ko/next has, etc.
13.	push out the bleeding edge, together with new tags that point into the pushed history.

In this example, the ko shorthand points at the Git maintainer’s repository at kernel.org, and looks like this:

bash

(in .git/config)
[remote "ko"]
\n
        url = kernel.org:/pub/scm/git/git.git
\n
        fetch = refs/heads/*:refs/remotes/ko/*
\n
        push = refs/heads/master
\n
        push = refs/heads/next
\n
        push = +refs/heads/seen
\n
        push = refs/heads/maint

REPOSITORY ADMINISTRATION

A repository administrator uses the following tools to set up and maintain access to the repository by developers.

update hook howto[1] has a good example of managing a shared central repository.

In addition there are a number of other widely deployed hosting, browsing and reviewing solutions such as:

Examples

We assume the following in /etc/services

bash

$ grep 9418 /etc/services
git             9418/tcp                # Git Version Control System

Run git-daemon to serve /pub/scm from inetd.

bash

$ grep git /etc/inetd.conf
git     stream  tcp     nowait  nobody \
\n
  /usr/bin/git-daemon git-daemon --inetd --export-all /pub/scm

The actual configuration line should be on one line.

Run git-daemon to serve /pub/scm from xinetd.

bash

$ cat /etc/xinetd.d/git-daemon
# default: off
# description: The Git server offers access to Git repositories
service git
{
\n
        disable = no
\n
        type            = UNLISTED
\n
        port            = 9418
\n
        socket_type     = stream
\n
        wait            = no
\n
        user            = nobody
\n
        server          = /usr/bin/git-daemon
\n
        server_args     = --inetd --export-all --base-path=/pub/scm
\n
        log_on_failure  += USERID
}

Check your xinetd(8) documentation and setup, this is from a Fedora system. Others might be different.

Give push/pull only access to developers using git-over-ssh.

bash

$ grep git /etc/passwd \n(1)\n
alice:x:1000:1000::/home/alice:/usr/bin/git-shell
bob:x:1001:1001::/home/bob:/usr/bin/git-shell
cindy:x:1002:1002::/home/cindy:/usr/bin/git-shell
david:x:1003:1003::/home/david:/usr/bin/git-shell
$ grep git /etc/shells \n(2)\n
/usr/bin/git-shell

1.	log-in shell is set to /usr/bin/git-shell, which does not allow anything but git push and git pull . The users require ssh access to the machine.
2.	in many distributions /etc/shells needs to list what is used as the login shell.

CVS-style shared repository.

bash

$ grep git /etc/group \n(1)\n
git:x:9418:alice,bob,cindy,david
$ cd /home/devo.git
$ ls -l \n(2)\n
\n
  lrwxrwxrwx   1 david git    17 Dec  4 22:40 HEAD -> refs/heads/master
\n
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 branches
\n
  -rw-rw-r--   1 david git    84 Dec  4 22:40 config
\n
  -rw-rw-r--   1 david git    58 Dec  4 22:40 description
\n
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 hooks
\n
  -rw-rw-r--   1 david git 37504 Dec  4 22:40 index
\n
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 info
\n
  drwxrwsr-x   4 david git  4096 Dec  4 22:40 objects
\n
  drwxrwsr-x   4 david git  4096 Nov  7 14:58 refs
\n
  drwxrwsr-x   2 david git  4096 Dec  4 22:40 remotes
$ ls -l hooks/update \n(3)\n
\n
  -r-xr-xr-x   1 david git  3536 Dec  4 22:40 update
$ cat info/allowed-users \n(4)\n
refs/heads/master       alice\|cindy
refs/heads/doc-update   bob
refs/tags/v[0-9]*       david

1.	place the developers into the same git group.
2.	and make the shared repository writable by the group.
3.	use update-hook example by Carl from Documentation/howto/ for branch policy control.
4.	alice and cindy can push into master, only bob can push into doc-update. david is the release manager and is the only person who can create and push version tags.

GIT

Part of the git(1) suite

NOTES

1.: update hook howto

NAME

SYNOPSIS

DESCRIPTION

INDIVIDUAL DEVELOPER (STANDALONE)

Examples

INDIVIDUAL DEVELOPER (PARTICIPANT)

Examples

INTEGRATOR

Examples

REPOSITORY ADMINISTRATION

Examples

GIT

NOTES