sane-project-website/cvs.html

181 wiersze
6.1 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>SANE - git Access</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="author" content="Henning Meier-Geinitz">
<meta name="keywords" content="sane, scanner, git, gitweb, development, unstable">
<meta name="description" content="SANE git server">
<link href="mailto:hmg-guest@users.alioth.debian.org" rev="made">
<link rel="icon" href="favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<center>
<a href="http://www.sane-project.org"><img src="images/sane.png"
alt="SANE" height="117" width="346" border="0"></a>
</center>
<center>
<h1><a
href="https://alioth.debian.org/scm/?group_id=30186"
target="_top">SANE - git Access</a></h1>
</center>
<hr>
<center>
<p>
<em>The SANE Project is in the process of relocating to GitLab.com.</em>
</p>
</center>
<p>
<a href="http://git-scm.com">git</a>, the version control
system invented by Linus Torvalds and used for the Linux
kernel among other things, is used to develop SANE. To get the
latest SANE software (sane-backends and sane-frontends) our
git repositories can be used. But keep in mind that the software in
git is not tested so the risk of bugs is much higher than with
stable releases.
</p>
<p>
There is development and anonymous git access. If you are not a
developer, please use the anonymous access methods as mentioned below.
</p>
<h2>Anonymous git Access (Read-Only)</h2>
<p>
The git repositories are available anonymously either through the
HTTP access method or the git-specific git protocol.
</p>
<p>
The HTTP access method should be used only if you are
restricted by a firewall that won't let you use either the git
protocol nor SSH. HTTP is slower and requires more bandwidth
than any other access methods.
</p>
<p>
You can clone from the following URIs:
<ul>
<li>HTTPS access method:
<ul>
<li>https://gitlab.com/sane-project/backends.git</li>
<li>https://gitlab.com/sane-project/frontends.git</li>
<li>https://anonscm.debian.org/git/sane/website.git</li>
</ul>
</li>
<li>git protocol (preferred):
<ul>
<li>git://anonscm.debian.org/git/sane/website.git</li>
</ul>
</li>
</ul>
</p>
<p>
If you just want to look at one file and don't want to download the
whole git repository, you can use browse the repository trees at:
<ul>
<li><a href="https://gitlab.com/sane-project/backends/tree/master">https://gitlab.com/sane-project/backends/tree/master</a></li>
<li><a href="https://gitlab.com/sane-project/frontends/tree/master">https://gitlab.com/sane-project/frontends/tree/master</a></li>
<li><a href="https://anonscm.debian.org/cgit/sane/website.git">https://anonscm.debian.org/cgit/sane/website.git</a></li>
</ul>
</p>
<h2>Developer Access to git (Read-Write)</h2>
<p>
If you intend to do <em>development</em>, <a
href="https://gitlab.com/users/sign_in">login at GitLab.com</a> and <a
href="https://gitlab.com/help/user/project/members/index.md#request-access-to-a-projectrequest">
request access</a> to the group or a specific project. Development git
access is done by SSH:
<ul>
<li>git@gitlab.com:sane-project/backends.git</li>
<li>git@gitlab.com:sane-project/frontends.git</li>
<li>ssh://yourlogin@anonscm.debian.org/git/sane/website.git</li>
</ul>
</p>
<p>
Available git repositories:
<ul>
<li>
<em>backends</em>: the main SANE package containing
the SANE libraries, all the backends and documentation.
</li>
<li>
<em>frontends</em>: various frontends for SANE,
including graphical frontends.
</li>
<li>
<em>website</em>: Our web pages. Before changing anything,
be sure you know what you do. Ask sane-devel, if in doubt.
The HTML pages are automatically updated when any change
is done to the tree. Also, the HTML lists of
scanners/backends supported by the git version of SANE is
automatically created when changing any .desc file.
</li>
</ul>
</p>
<p>
The rules are pretty simple: If you change anything in your backend, do
whatever you want. Just don't break compilation :-). Don't change
backends of other active developers. For backends of non-active
developers or any other code you should either know what you are doing
or ask on sane-devel if the change is acceptable. Fixing spelling
mistakes or broken links in the HTML pages is appreciated. Before doing
major changes please ask on sane-devel.
</p>
<p>
When committing work to sane-backends or sane-frontends, make sure
to write a descriptive commit message. The format is simple, a short
single line summary, optionally followed by a longer explanation of why
things were changed. For large changes, including a summary of what
changed may be helpful too. Example:
</p>
<pre>
niash.c: Add argument screening to sane_control_option
This prevents access to non-existing array elements as well as
potential NULL dereferences.
Fixes #315132.
</pre>
<p>
Commit messages will be collected in a ChangeLog file for inclusion
in the release by the release manager. There is no need to update
the ChangeLog file yourself. People using the "bleeding edge" are
supposed to have convenient access to the <tt>git log</tt> output.
</p>
<h2>sane-commit Mailing list</h2>
<p>
If you are interested in the changes to the SANE git trees, subscribe to
the <a
href="http://lists.alioth.debian.org/mailman/listinfo/sane-commit"
target="_top">sane-commit mailing list</a>.
</p>
<hr>
<p>
<a href="/">SANE homepage</a><br>
<a href="imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>
<!-- LocalWords: co
-->