[cairo-commit] [cairo-www] src/cairomm.mdwn
cworth at freedesktop.org
Fri Apr 11 09:49:30 PDT 2008
src/cairomm.mdwn | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Author: Carl Worth <cworth at freedesktop.org>
Date: Fri Apr 11 09:49:29 2008 -0700
web commit by murrayc: Change gitweb links to cgit, which seems much more aimed at humans.
diff --git a/src/cairomm.mdwn b/src/cairomm.mdwn
index 46dd2eb..80f80d2 100644
@@ -17,7 +17,7 @@ You can download released versions of cairomm from the
## Git Repository
If you want bleeding-edge code, (or if you want to help out with development of cairomm), you can also
-check out cairomm from git, which you can also [browse online via gitweb](http://gitweb.cairographics.org/?p=cairomm.git;a=tree).
+check out cairomm from git, which you can also [browse online](http://cgit.freedesktop.org/cairomm/tree/).
Anybody can checkout the latest source code **anonymously** with the following command
@@ -43,7 +43,7 @@ documentation](/manual/) as well.
In addition to the API documentation, there are several small example
programs which ship with cairomm and demonstrate some of the basic
functionality. These examples are in the examples/ directory of the
-release tarball or can be [browsed online](http://gitweb.cairographics.org/?p=cairomm.git;a=tree;f=examples).
+release tarball or can be [browsed online](http://cgit.freedesktop.org/cairomm/tree/examples).
There is also some tutorial-like documentation available in the gtkmm manual. The [Drawing Area chapter](http://gtkmm.org/docs/gtkmm-2.4/docs/tutorial/html/ch15.html) introduces some basic cairomm drawing concepts. Although the documentation is about using cairomm with gtkmm, most of the concepts apply whether you're using gtkmm or not. In addition, you may find it helpful to reference the [[C_cairo_tutorial|tutorial]]. Most of the concepts will translate directly from the C API to the C++ API with very few changes.
@@ -84,6 +84,7 @@ When you've made some changes, you can commit them to your local repository with
git commit -a -m "Commit message"
The commit message should generally be a copy/paste of your entry in the ChangeLog. Always remember to make an entry in the ChangeLog, in the style of the existing ChangeLog entries. It's particularly important to mention what you changed in each file and to mention the overall aim of your changes, including any relevant bugzilla bug number. The [moap](http://thomas.apestaart.org/moap/trac) tool can help you to create ChangeLog entries with git or other popular source control systems. Use:
moap changelog prepare -c
More information about the cairo-commit