bagder: curl-www/auto _contribute.html, NONE, 1.1 _internals.html, NONE, 1.1 _runtests.html, NONE, 1.1 _source.html, NONE, 1.1 _testcurl.html, NONE, 1.1

[email protected] Sat, 09 Oct 2010 10:18:27 +0000
Newsgroups	gmane.comp.web.curl.www.cvs
Message-ID	<[email protected]>
Update of /cvsroot/curl/curl-www/auto
In directory giant.haxx.se:/var/tmp/cvs-serv13806

Added Files:
	_contribute.html _internals.html _runtests.html _source.html 
	_testcurl.html 
Log Message:
dev related docs moved into the dev section


--- NEW FILE: _testcurl.html ---
#include "_doctype.html"
<HTML>
<HEAD> <TITLE>cURL - Automatic Test</TITLE>
#include "css.t"
#include "../docs/manpage.t"
</HEAD>

#define DEVEL_TESTCURL
#define CURL_URL dev/testcurl.html

#include "_menu.html"
#include "setup.t"

WHERE2(Development, "/dev/", testcurl.pl)

TITLE(testcurl.1 the man page)
<div class="relatedbox">
<b>Related:</b>
<br><a href="/docs/manpage.html">curl.1</a>
<br><a href="runtests.html">runtests.1</a>
<br><a href="/docs/manual.html">Manual</a>
<br><a href="/docs/faq.html">FAQ</a>
<br><a href="/docs/httpscripting.html">HTTP Scripting</a>
</div>

#include "testcurl.dump"

#include "_footer.html"

</BODY>
</HTML>


--- NEW FILE: _source.html ---
#include "_doctype.html"
<HEAD> <TITLE>cURL - Source Code</TITLE>
#include "css.t"
</HEAD>

#define DEVEL_SOURCE
#include "_menu.html"
#include "setup.t"

WHERE2(Development, "/dev/", Source Code)

TITLE(Sources code control)
<p>
<div class="relatedbox">
<b>Related:</b>
<br><a href="http://cool.haxx.se/curl-daily/">Daily Snaphots</a>
<br><a href="/docs/install.html">Build Instructions</a>
</div>
<p>
 In the cURL project we've been using CVS since the start of the project, and
 around its 12th birthday (March 20, 2010) we started converting over to the
 new git repository. The transition is still incomplete!

TITLE(<b>Browse</b> the Sources)
<p>
  <a href="http://github.com/bagder/curl">Browse the source repository</a> (on github.com)

TITLE(<b>Get</b> the Sources)
<p>
  The curl sources are kept in a git repository. You can get the most recent
  curl source files from there at any time. git is the version control system
  we use for the curl project. All files in the release archive that aren't
  generated from other files are kept there, to allow full backtracking of
  older versions. To use git you need a git client, get yours from <a
  href="http://git-scm.com/">git-scm.com</a>.  Windows users might
  fancy <a href="http://code.google.com/p/tortoisegit/">tortoisegit</a> or <a
  href="http://code.google.com/p/msysgit/">msysgit</a>.
<p>
  This is mostly a feature for you who really want to have a peek in how the
  current development version looks like, and not if you just want to download
  a version to run. If you just want to download a tar or binary archive, <a
  href="/download.html">go here</a>.
<p>
  If you want to use the git server, run:
<pre>
  git clone git://github.com/bagder/curl.git
</pre>

  or use the Swedish mirror server:

<pre>
  git clone git://curl.haxx.se/curl
</pre>

 <b>Note</b> that this will create a curl subdirectory.
<p>
  If you at a later time want to get the updated set of files, just cd into
  this directory and run
<pre>
  git pull
</pre>
<p>
  If a proxy, firewall or something else is preventing you from using git to
  get the latest sources, you can get the sources off the repo using HTTP like:
<pre>
  git clone http://github.com/bagder/curl.git
</pre>
 You can also opt to download a <a
 href="http://cool.haxx.se/curl-daily/">daily snapshot</a>.

TITLE(<b>Compile and Build</b> the Sources)
<p>
 When you checkout the sources, you get a file named CVS-INFO in the source
 root that describes how to proceed to compile and build them.

TITLE(<b>Change</b> the Sources)
<p>
 If you are about to do a lot of modifications, discuss it on the curl or
 libcurl mailing list in advance and please consider to use git directly to do
 the changes and provide the necessary patches back to the project!

<p>
 If you want to push to the repository, you need to have it cloned using:
<pre>
  git clone [email protected]:bagder/curl.git
</pre>
<p>
 This also requires that you have a github account and have been added to the
 project as a collaborator by Daniel.

#include "_footer.html"

</BODY>
</HTML>

--- NEW FILE: _contribute.html ---
#include "_doctype.html"
<HTML>
<HEAD> <TITLE>cURL - CONTRIBUTE</TITLE>
#include "css.t"
</HEAD>

#define DEVEL_CONTRIBUTE
#define CURL_URL dev/contribute.html

#include "_menu.html"
#include "setup.t"

WHERE2(Development, "/dev/", Contribute)

TITLE(Contribute -- How to Contribute Code)
<div class="relatedbox">
<b>Related:</b>
<br><a href="/mail/">Mailing Lists</a>
<br><a href="internals.html">Internals</a>
</div>

#include "contribute.t"

#include "_footer.html"

</BODY>
</HTML>


--- NEW FILE: _runtests.html ---
#include "_doctype.html"
<HTML>
<HEAD> <TITLE>cURL - Run curl tests</TITLE>
#include "css.t"
#include "../docs/manpage.t"
</HEAD>

#define DEVEL_RUNTESTS
#define CURL_URL dev/runtests.html

#include "_menu.html"
#include "setup.t"

WHERE2(Development, "/dev/", runtests.pl)

TITLE(runtests.1 the man page)
<div class="relatedbox">
<b>Related:</b>
<br><a href="/docs/manpage.html">man page</a>
<br><a href="testcurl.html">testcurl.1</a>
<br><a href="/docs/faq.html">FAQ</a>
<br><a href="/docs/httpscripting.html">HTTP Scripting</a>
</div>

#include "runtests.dump"

#include "_footer.html"

</BODY>
</HTML>


--- NEW FILE: _internals.html ---
#include "_doctype.html"
<HTML>
<HEAD> <TITLE>cURL - Internal Design</TITLE>
#include "css.t"
</HEAD>

#define DEVEL_INTERNALS
#define CURL_URL dev/internals.html

#include "_menu.html"
#include "setup.t"

WHERE2(Development, "/dev/", Internals)

TITLE(INTERNALS -- how things work inside)

<pre>
#include "internals.t"
</pre>

#include "_footer.html"

</BODY>
</HTML>