/usr/share/doc/wireshark-doc/wsdg_html_chunked/ChSrcGitRepository.html is in wireshark-doc 2.0.2+ga16e22e-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>3.2. The Wireshark Git repository</title><link rel="stylesheet" type="text/css" href="ws.css"><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"><link rel="home" href="index.html" title="Wireshark Developer’s Guide"><link rel="up" href="ChapterSources.html" title="Chapter 3. Work with the Wireshark sources"><link rel="prev" href="ChapterSources.html" title="Chapter 3. Work with the Wireshark sources"><link rel="next" href="ChSrcObtain.html" title="3.3. Obtain the Wireshark sources"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">3.2. The Wireshark Git repository</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChapterSources.html">Prev</a> </td><th width="60%" align="center">Chapter 3. Work with the Wireshark sources</th><td width="20%" align="right"> <a accesskey="n" href="ChSrcObtain.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ChSrcGitRepository"></a>3.2. The Wireshark Git repository</h2></div></div></div><p><a class="ulink" href="http://git-scm.com/" target="_top">Git</a> is used to keep track of the changes made to the
Wireshark source code. The code is stored inside Wireshark project’s Git
repository located at a server at the wireshark.org domain.</p><p>Changes to the official repository are managed using the
<a class="ulink" href="https://code.google.com/p/gerrit/" target="_top">Gerrit</a> code review sytem. Gerrit
makes it easy to test and discuss changes before they are
pushed to the main repository. For an overview of Gerrit see the
<a class="ulink" href="https://code.wireshark.org/review/Documentation/intro-quick.html" target="_top">Quick
Introduction</a>.</p><p><b>Why Git? </b>Git is a fast, flexible way of managing source code. It allows large
scale distributed development and ensures data integrity.</p><p><b>Why Gerrit? </b>Gerrit makes it easy to contribute. You can sign in with any OpenID
provider and push your changes. It’s usable from both the web and
command line and is integrated with many popular tools.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note: Git is our third revision conrol system"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="wsdg_graphics/note.svg"></td><th align="left">Git is our <span class="strong"><strong>third</strong></span> revision conrol system</th></tr><tr><td align="left" valign="top"><p>Wireshark originally used <a class="ulink" href="http://www.nongnu.org/cvs/" target="_top">Concurrent Versions System</a>
(CVS) and migrated to <a class="ulink" href="http://subversion.apache.org/" target="_top">Subversion</a> in July 2004.
The Subversion repository was subsequently migrated to Git in January 2014.</p></td></tr></table></div><p>Using Wireshark’s Git repository you can:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Keep your private sources up to date with very little effort
</li><li class="listitem">
Get a mail notification when the official source code changes
</li><li class="listitem">
Get the source files from any previous release (or any other point in time)
</li><li class="listitem">
Have a quick look at the sources using a web interface
</li><li class="listitem">
See which person changed a specific piece of code
</li><li class="listitem">
and much more
</li></ul></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="ChSrcWebInterface"></a>3.2.1. The web interface to the Git repository</h3></div></div></div><p>If you need a quick look at the Wireshark source code you can
browse the most recent file versions in the master branch using Gitweb:</p><p><a class="ulink" href="https://code.wireshark.org/review/gitweb?p=wireshark.git;a=tree" target="_top">https://code.wireshark.org/review/gitweb?p=wireshark.git;a=tree</a></p><p>You can also view commit logs, branches, tags, and past revisions:</p><p><a class="ulink" href="https://code.wireshark.org/review/gitweb?p=wireshark.git" target="_top">https://code.wireshark.org/review/gitweb?p=wireshark.git</a></p><p>Like most revision control systems, Git uses
<a class="ulink" href="http://en.wikipedia.org/wiki/Branching_%28revision_control%29" target="_top">branching</a> to
manange different copies of the source code and allow parallel development.
Wireshark uses the following branches for official releases:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<span class="emphasis"><em>master</em></span>: Main feature development and odd-numbered "feature" releases.
</li><li class="listitem">
<span class="emphasis"><em>master-x.y</em></span>: Stable release maintenance. For example, master-1.10 is used
to manage the 1.10.x official releases.
</li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ChapterSources.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ChapterSources.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ChSrcObtain.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Work with the Wireshark sources </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3.3. Obtain the Wireshark sources</td></tr></table></div></body></html>
|