Commit ff9854a7 authored by Paolo Borelli's avatar Paolo Borelli

Update HACKING and README for git

Some updates to HACKING and README for the new git repo
parent 30667e0d
guidelines for gedit
====================
Please don't commit directly to the subversion repository unless
gedit source code is maintained using the git version control system
and is available at the following location:
git://git.gnome.org/gedit
Or if you have an account on GNOME servers:
ssh://USERNAME@git.gnome.org/git/gedit
A Web Interface is available at:
http://git.gnome.org/cgit/gedit
Please don't commit directly to the git repository unless
you have been given the green light to commit freely to gedit.
When in doubt assume you haven't ;-).
......@@ -18,5 +31,35 @@ your help, I just want to review these fixes before applying.
If you are a "build sheriff", feel free to commit fixes for build and
configure (please, send me an e-mail with the patch you have applied).
Thanks
Paolo
When committing to the gedit git repository make sure to include a
meaningful commit message. Changes without a sufficient commit message
will be reverted. Commit messages should have the following format:
=== begin example commit ===
Short explanation of the commit
Longer explanation explaining exactly what's changed, whether any
external or private interfaces changed, what bugs were fixed (with bug
tracker reference if applicable) and so forth. Be concise but not too brief.
=== end example commit ===
- Always add a brief description of the commit to the _first_ line of
the commit and terminate by two newlines (it will work without the
second newline, but that is not nice for the interfaces).
- First line (the brief description) must only be one sentence and
should start with a capital letter unless it starts with a lowercase
symbol or identifier. Don't use a trailing period either. Don't exceed
72 characters.
- The main description (the body) is normal prose and should use normal
punctuation and capital letters where appropriate. Normally, for patches
sent to a mailing list it's copied from there.
- When committing code on behalf of others use the --author option, e.g.
git commit -a --author "Joe Coder <joe@coder.org>" and --signoff.
Thanks,
The gedit team.
......@@ -53,9 +53,9 @@ The official web site is:
http://www.gedit.org
You can download the latest gedit tarball from the gnome ftp server:
You can download the latest gedit tarball from:
http://ftp.gnome.org/pub/GNOME/sources/gedit/
http://download.gnome.org/sources/gedit/
Information about gedit mailing lists can be found at
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment