gnomeweb-wml r5821 - trunk/www.gnome.org/projects/gtksourceview
- From: paolo svn gnome org
- To: svn-commits-list gnome org
- Subject: gnomeweb-wml r5821 - trunk/www.gnome.org/projects/gtksourceview
- Date: Tue, 5 Feb 2008 13:23:42 +0000 (GMT)
Author: paolo
Date: Tue Feb 5 13:23:41 2008
New Revision: 5821
URL: http://svn.gnome.org/viewvc/gnomeweb-wml?rev=5821&view=rev
Log:
It is now a valid XHTML page.
Modified:
trunk/www.gnome.org/projects/gtksourceview/development.html
Modified: trunk/www.gnome.org/projects/gtksourceview/development.html
==============================================================================
--- trunk/www.gnome.org/projects/gtksourceview/development.html (original)
+++ trunk/www.gnome.org/projects/gtksourceview/development.html Tue Feb 5 13:23:41 2008
@@ -47,7 +47,7 @@
<div id="content">
- <h2>Contributing</h2>
+ <h2><a name="Contributing">Contributing</a></h2>
<p>GtkSourceView development relies on voluntary contributions and everyone
is invited to help.
</p>
@@ -56,14 +56,14 @@
on <a href="#IRC">IRC</a> and/or
send a message to the GtkSourceView <a href="#MailingLists">mailing list</a> and offer your help.
</p>
- <p>See the <a href="http://svn.gnome.org/viewvc/gtksourceview/trunk/HACKING?view=markup"">HACKING</a>
+ <p>See the <a href="http://svn.gnome.org/viewvc/gtksourceview/trunk/HACKING?view=markup">HACKING</a>
file for information about the GtkSourceView
coding style and <a href="http://subversion.tigris.org/">Subversion</a> usage guidelines.
</p>
<h2><a name="BugReporting">Bug reporting</a></h2>
<p>Bugs should be reported to the <a href="http://bugzilla.gnome.org">GNOME
- bug tracking system</a>, product <a href="http://bugzilla.gnome.org/browse.cgi?product=gtksourceview">gtksourceview</a>.
+ bug tracking system</a>, product <a href="http://bugzilla.gnome.org/browse.cgi?product=gtksourceview">gtksourceview</a>.</p>
<p>You will need an email address to register (if you haven't already)
before you can use the system to file a new bug report.</p>
@@ -75,7 +75,7 @@
helps us prioritize bugs.</p>
<h2><a name="Patches">Patches</a></h2>
- <p>Patches should be submitted to the <a href="http://bugzilla.gnome.org">bug tracking system</a>.
+ <p>Patches should be submitted to the <a href="http://bugzilla.gnome.org">bug tracking system</a>.</p>
<p>If the patch fixes a known bug, add the patch as an attachment to the corresponding bug
report. Otherwise, enter a new bug report that describes the problem the patch
@@ -83,7 +83,7 @@
<p>Patches should be in unified diff form (use the -up options of GNU diff)
and should follow the coding style described in the
- <a href="http://svn.gnome.org/viewvc/gtksourceview/trunk/HACKING?view=markup"">HACKING</a>
+ <a href="http://svn.gnome.org/viewvc/gtksourceview/trunk/HACKING?view=markup">HACKING</a>
file.
</p>
<p>See the <a href="http://live.gnome.org/GnomeLove/SubmittingPatches">Submitting Patches</a> page
@@ -101,7 +101,7 @@
<a href="http://mail.gnome.org/archives/gnome-devtools/">gnome-devtools archives</a>.</p>
<h2><a name="IRC">Internet Relay Chat</a></h2>
- <p>You can find the developers on <b>#gedit</b> channel at <b>irc.gnome.org</b>.
+ <p>You can find the developers on <b>#gedit</b> channel at <b>irc.gnome.org</b>.</p>
<h2><a name="Wiki">Wiki</a></h2>
<p>We have a Wiki for drafting, designing and proposing GtkSourceView
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]