Hi,
Thanks for working on this.
Min Xu wrote:
I am not familiar with git... but isn't there
access restrictions
on commit to the git similar to svn?
An important difference between git and svn is that git is
distributed instead of centralized.
This means that every developer starts with an identical copy "a clone"
of the
osmocom.org repository in their worktree, and everyone can create
commits locally. Complete commits can then be transfered between
developers by a few different means, one of which is email.
This significantly reduces workload of project maintainers, since they
can include well-formed commits from other developers very quickly.
A git commit includes both author and commiter information, and the
commit message, so one effect of using git is that new developers can
easily contribute directly to the main repository, by sending a
commit they have created locally via email to the project.
If you can send email on the workstation where you run git, you can
use the git send-email command (with appropriate parameters). If you
need a separate patch file to attach in a standalone email program
you can run git format-patch (with appropriate parameters, such as -1
in order to generate a patch file for the last 1 commit).
Please configure git with your name, and please follow the common
practise for commit messages; on line 1 a short (<=72 chars) summary,
line 2 blank, line 3 and onwards a longer description and rationale
for the change. Try to keep lines 3 and later <=74 chars.
I recommend the book "Pro Git" at
http://git-scm.com/book as well as
the more lightweight Git Reference at
http://gitref.org/ and the #git
IRC channel on
irc.freenode.net for community help.
//Peter