mirror of
git://sourceware.org/git/libabigail.git
synced 2025-01-13 04:41:28 +00:00
e5cc86a9b7
I felt this file needed a little bit of clean-up. There we go. * CONTRIBUTING: Cleanup. Signed-off-by: Dodji Seketeli <dodji@redhat.com>
95 lines
3.1 KiB
Plaintext
95 lines
3.1 KiB
Plaintext
Contact
|
|
=======
|
|
|
|
The project homepage is at https://sourceware.org/libabigail
|
|
|
|
The current libabigail source code can be checked out with:
|
|
git clone git://sourceware.org/git/libabigail
|
|
|
|
The mailing list to send messages and patches to is
|
|
libabigail@sourceware.org.
|
|
|
|
The archives of that list are available at http://sourceware.org/ml/libabigail.
|
|
|
|
File bugs
|
|
=========
|
|
|
|
Bugs are to be filled in bugzilla at
|
|
https://sourceware.org/bugzilla/enter_bug.cgi?product=libabigail
|
|
|
|
Writing and sending patches
|
|
============================
|
|
|
|
Please supply patches using git format-patch and git send-email. If
|
|
you don't know how to use git, send-email, fine. Just use your
|
|
favorite email client, attach the patch to a nice message, and send us
|
|
the message.
|
|
|
|
Patches have to be sent by email to libabigail@sourceware.org.
|
|
|
|
Please read the file COMMIT-LOG-GUIDELINES in the source tree to learn
|
|
about how to write the commit log accompanying the patch.
|
|
|
|
Make sure you sign your patch. To learn about signing, please read
|
|
below.
|
|
|
|
Sign your work
|
|
==============
|
|
|
|
To facilitate tracking of who did what, we've adopted a "sign-off"
|
|
procedure for patches based on the procedure used by the Linux kernel
|
|
project.
|
|
|
|
The sign-off is a simple line at the end of the explanation for the
|
|
patch, which certifies that you wrote it or otherwise have the right
|
|
to pass it on as a patch under an appropriate license. The rules are
|
|
pretty simple: if you can certify the below:
|
|
|
|
Developer's Certificate of Origin
|
|
|
|
By making a contribution to this project, I certify that:
|
|
|
|
(a) The contribution was created in whole or in part by me,
|
|
and I have the right to submit the contribution under the
|
|
license indicated in, or otherwise designated as being
|
|
applicable to, the file.
|
|
|
|
(b) The contribution was provided directly to me by some other
|
|
person who certified (a), and I have not modified it.
|
|
|
|
(c) I understand and agree that the project and the
|
|
contribution are public and that a record of the
|
|
contribution (including all personal information I submit
|
|
with it, including my sign-off) is maintained indefinitely
|
|
and may be redistributed.
|
|
|
|
then you just add a line saying
|
|
|
|
Signed-off-by: Random J Developer <random@developer.example.org>
|
|
|
|
using your real name (sorry, no pseudonyms or anonymous contributions.)
|
|
|
|
git commit --signoff will add such a Signed-off-by line at the end of
|
|
the commit log message for you.
|
|
|
|
Modifying the website
|
|
=====================
|
|
|
|
The source code of the website of libabigail is stored in CVS (sigh,
|
|
yeah, that is so old school). You can check out that web source code
|
|
by doing:
|
|
|
|
CVS_RSH=ssh cvs -z9 -d :ext:user@sourceware.org:/cvs/libabigail/ co htdocs
|
|
|
|
where 'user' is your username on the sourceware system.
|
|
Alternatively, you can check out the the web source code anonymously,
|
|
if you don't have any user account on the sourceware system by doing:
|
|
|
|
export CVSROOT=:pserver:anoncvs@cygwin.com:/cvs/libabigail
|
|
cvs login
|
|
(the CVS anonymous password to use is "anoncvs")
|
|
cvs checkout htdocs
|
|
|
|
|
|
Happy Hacking!
|