6
$ git clone git://git.freedesktop.org/git/DeviceKit/DeviceKit-power.git
8
- checkouts if you got an ssh account on fd.o (username@ is optional)
10
$ git clone ssh://[username@]git.freedesktop.org/git/DeviceKit/DeviceKit-power.git
12
- commit to local repository
16
- push local repository to master repository at fd.o (remember most patches
17
requires review at the mailing list)
21
- pull changes from master repository at fd.o
25
- diff of working tree versus local repository
29
- diff of local repository vs. master repository at fd.o
31
synchronize with upstream repo:
34
(possibly merge changes)
37
$ git diff origin HEAD
39
- influential environment variables (set these in e.g. .bash_profile)
41
export GIT_AUTHOR_NAME='Your Full Name'
42
export GIT_COMMITTER_NAME='Your Full Name'
43
export GIT_COMMITTER_EMAIL=youremail@domain.net
44
export GIT_AUTHOR_EMAIL=youremail@domain.net
48
http://www.kernel.org/pub/software/scm/git/docs/
54
- Commit messages should be of the form (the five lines between the
55
lines starting with ===)
57
=== begin example commit ===
58
short explanation of the commit
60
Longer explanation explaining exactly what's changed, whether any
61
external or private interfaces changed, what bugs were fixed (with bug
62
tracker reference if applicable) and so forth. Be concise but not too brief.
63
=== end example commit ===
65
- Always add a brief description of the commit to the _first_ line of
66
the commit and terminate by two newlines (it will work without the
67
second newline, but that is not nice for the interfaces).
69
- First line (the brief description) must only be one sentence and
70
must not start with a capital letter. Don't use a trailing period
73
- The main description (the body) is normal prose and should use normal
74
punctuation and capital letters where appropriate. Normally, for patches
75
sent to a mailing list it's copied from there.
77
- When committing code on behalf of others use the --author option, e.g.
78
git commit -a --author "Joe Coder <joe@coder.org>"
83
- Please follow the coding style already used.
85
- Write docs for all functions and structs and so on. We use gtkdoc format.
87
- All external interfaces (network protocols, file formats, etc.)
88
should have documented specifications sufficient to allow an
89
alternative implementation to be written. Our implementation should
90
be strict about specification compliance (should not for example
91
heuristically parse a file and accept not-well-formed
92
data). Avoiding heuristics is also important for security reasons;
93
if it looks funny, ignore it (or exit, or disconnect).
added
removed
HACKING
