brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[docs] Fix typos and remove mentions of SVN

Browse Source 
Signed-off-by: Emmanuele Bassi <ebassi@linux.intel.com>
This commit is contained in:
Evan Martin 2009-07-12 01:38:40 +01:00 committed by Emmanuele Bassi
parent efc16a4d90
commit ea56a5e7a8
3 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
HACKING
View File

@ -93,7 +93,8 @@ RELEASES
In making a new release;
- Check out a fresh copy from SVN.
- Verify your working directory is fresh; i.e., check out a fresh copy
or "git reset --hard release_branch && git clean -f".
- Verify versioning in configure.ac, increasing relevant
clutter_major_version/clutter_minor_version/clutter_micro_version

2
clutter/cogl/cogl-path.h
View File

@ -169,7 +169,7 @@ void cogl_path_rel_line_to (float x,
* @center_x: X coordinate of the elliptical arc center
* @center_y: Y coordinate of the elliptical arc center
* @radius_x: X radius of the elliptical arc
* @radius_y: Y radious of the elliptical arc
* @radius_y: Y radius of the elliptical arc
* @angle_1: Angle in the unit-circle at which the arc begin
* @angle_2: Angle in the unit-circle at which the arc ends
*

2
tests/README
View File

@ -8,5 +8,5 @@ The micro-bench/ tests should be focused perfomance test, ideally testing a sing
The interactive/ tests are any tests whos status can not be determined without a user looking at some visual output, or providing some manual input etc. This covers most of the original Clutter tests. Ideally some of these tests will be migrated into the conformance/ directory so they can be used in automated nightly tests.
Other notes:
All tests should ideally include a detailed description in the source explaining exactly what the test is for, how the test was designed to work, and possibly a rationale for the aproach taken for testing.
All tests should ideally include a detailed description in the source explaining exactly what the test is for, how the test was designed to work, and possibly a rationale for the approach taken for testing.