[tor-commits] [webwml/master] cgit version of blob_plain/HEAD:/ and blob/HEAD:/

sebastian at torproject.org sebastian at torproject.org
Thu Dec 11 13:01:25 UTC 2014


commit 1700644e004b850b51a8ae1410622f2f2130aecd
Author: Matt Pagan <matt at pagan.io>
Date:   Wed Dec 10 08:56:08 2014 -0600

    cgit version of blob_plain/HEAD:/ and blob/HEAD:/
---
 about/en/corepeople.wml              |    2 +-
 about/en/jobs-coredev.wml            |    2 +-
 about/en/jobs-pluggabletransport.wml |    2 +-
 docs/en/faq.wml                      |    8 ++++----
 docs/en/pluggable-transports.wml     |   10 +++++-----
 docs/en/tor-doc-relay.wml            |    2 +-
 docs/torbutton/en/index.wml          |    6 +++---
 eff/en/tor-legal-faq.wml             |    2 +-
 getinvolved/en/volunteer.wml         |    2 +-
 projects/en/obfsproxy.wml            |    2 +-
 projects/en/torbrowser.wml           |    4 ++--
 projects/en/tordnsel.wml             |    2 +-
 projects/en/vidalia.wml              |    2 +-
 13 files changed, 23 insertions(+), 23 deletions(-)

diff --git a/about/en/corepeople.wml b/about/en/corepeople.wml
index 9e9dec8..c263145 100644
--- a/about/en/corepeople.wml
+++ b/about/en/corepeople.wml
@@ -284,7 +284,7 @@
           <dt>Mike Perry, Tor Browser and Tor Performance
           Developer</dt> <dd>Lead developer on Tor Browser, developer
           of <a href="<page docs/torbutton/index>">Torbutton</a>, author of <a
-          href="https://gitweb.torproject.org/torflow.git/blob/HEAD:/README">TorFlow</a>.
+          href="https://gitweb.torproject.org/torflow.git/tree/README">TorFlow</a>.
           Runs one of the directory authorities.</dd>
 
           <dt>Sina Rabbani, Advocate</dt>
diff --git a/about/en/jobs-coredev.wml b/about/en/jobs-coredev.wml
index 6564896..acd324b 100644
--- a/about/en/jobs-coredev.wml
+++ b/about/en/jobs-coredev.wml
@@ -80,7 +80,7 @@ and scramble to implement last-minute anticensorship schemes, or to
 deploy urgent security updates. You'd also be reviewing other people's
 code and designs, and looking for ways to improve it. For an idea of
 the breadth and depth of the work you'd be doing, have a look at <a
-href="https://gitweb.torproject.org/tor.git/blob/HEAD:/ChangeLog">the
+href="https://gitweb.torproject.org/tor.git/tree/ChangeLog">the
 ChangeLog file from the Tor source distribution</a>.
 </p>
 
diff --git a/about/en/jobs-pluggabletransport.wml b/about/en/jobs-pluggabletransport.wml
index 627c134..dceb8fa 100644
--- a/about/en/jobs-pluggabletransport.wml
+++ b/about/en/jobs-pluggabletransport.wml
@@ -83,7 +83,7 @@ transports</a> and their
 
 <li>
 Have run the
-<a href="https://gitweb.torproject.org/flashproxy.git/blob/HEAD:/README">sample
+<a href="https://gitweb.torproject.org/flashproxy.git/tree/README">sample
 commands in the README</a>, and made notes about the process. One of
 your early tasks will be to do such testing so that the packages you
 make will be effectively usable.
diff --git a/docs/en/faq.wml b/docs/en/faq.wml
index e6e426a..cd9e9d9 100644
--- a/docs/en/faq.wml
+++ b/docs/en/faq.wml
@@ -1659,7 +1659,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
     <h3><a class="anchor" href="#TBBSourceCode">Where is the source code for the bundle? How do I verify a build?</a></h3>
 
     <p>
-    Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build</a>.
+    Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build</a>.
     </p>
 
 
@@ -2384,7 +2384,7 @@ too.
     Linux-based Tor nodes have another option at their disposal: they can
     prioritize Tor traffic below other traffic on their machine, so that
     their own personal traffic is not impacted by Tor load. A <a
-    href="https://gitweb.torproject.org/tor.git/blob/HEAD:/contrib/operator-tools/linux-tor-prio.sh">script
+    href="https://gitweb.torproject.org/tor.git/tree/contrib/operator-tools/linux-tor-prio.sh">script
     to do this</a> can be found in the Tor source distribution's contrib
     directory.
     </p>
@@ -3291,7 +3291,7 @@ diversity,
     testing network with about 10 instances of Tor. Every instance of Tor
     binds to one or two ports on localhost (127.0.0.1) and all Tor
     communication is done over the loopback interface. The <a
-    href="https://gitweb.torproject.org/chutney.git/blob/HEAD:/README">Chutney
+    href="https://gitweb.torproject.org/chutney.git/tree/README">Chutney
     README</a> is a good starting point for getting it up and running.
     </p>
     <p>
@@ -3755,7 +3755,7 @@ destination, rather than just one chance.
     </p>
     <p>
 The actual content of these fixed size cells is
-<a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/tor-spec.txt">
+<a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">
 documented in the main Tor spec</a>, section 3.
     </p>
     <p>
diff --git a/docs/en/pluggable-transports.wml b/docs/en/pluggable-transports.wml
index 2892916..5b079ed 100644
--- a/docs/en/pluggable-transports.wml
+++ b/docs/en/pluggable-transports.wml
@@ -28,7 +28,7 @@
     client and the bridge will see innocent-looking transformed traffic
     instead of the actual Tor traffic.
     External programs can talk to Tor clients and Tor bridges using the <a
-href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/pt-spec.txt">pluggable
+href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable
 transport API</a>, to make it easier to build interoperable programs.
     </p>
 
@@ -38,11 +38,11 @@ transport API</a>, to make it easier to build interoperable programs.
 
     <li><a href="<page projects/obfsproxy>"><b>Obfsproxy</b></a> is a Python framework for implementing new
     pluggable transports. It uses Twisted for its networking needs, and
-    <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/blob/HEAD:/README.rst">pyptlib</a>
+    <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/tree/README.rst">pyptlib</a>
     for some pluggable transport-related features. It supports the
-    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs2/obfs2-protocol-spec.txt">obfs2</a>
+    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs2/obfs2-protocol-spec.txt">obfs2</a>
     and
-    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
+    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
     pluggable transports. Maintained by asn. <br>
     Status: <a href="#download">Deployed</a>
     </li>
@@ -87,7 +87,7 @@ transport API</a>, to make it easier to build interoperable programs.
     is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
     but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a>
     technique for public key obfuscation, and the
-    <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/216-ntor-handshake.txt">ntor protocol</a>
+    <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake.txt">ntor protocol</a>
     for one-way authentication. This results in a faster protocol. Written in Go.
     Maintained by Yawning Angel. <br>
     Status: <e>Coming soon</em>
diff --git a/docs/en/tor-doc-relay.wml b/docs/en/tor-doc-relay.wml
index a2069f2..cda8eee 100644
--- a/docs/en/tor-doc-relay.wml
+++ b/docs/en/tor-doc-relay.wml
@@ -81,7 +81,7 @@
     options are described in <a href="<page docs/faq>#LimitTotalBandwidth">these</a>
     <a href="<page docs/faq>#BandwidthShaping">FAQ entries</a>.</p>
 
-    <p>See the <a href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/src/config/torrc.sample.in">sample
+    <p>See the <a href="https://gitweb.torproject.org/tor.git/plain/src/config/torrc.sample.in">sample
     torrc file</a> and the <a
     href="<page docs/tor-manual>">man
     page</a> for other Tor options you may want to set.</p>
diff --git a/docs/torbutton/en/index.wml b/docs/torbutton/en/index.wml
index 703dd95..b773598 100644
--- a/docs/torbutton/en/index.wml
+++ b/docs/torbutton/en/index.wml
@@ -112,9 +112,9 @@
     <strong>Bug Reports:</strong> <a href="https://trac.torproject.org/projects/tor/report/14">Torproject Bug Tracker</a><br/>
     <strong>Documents:</strong> 
     <b>[</b> 
-    <a href="https://gitweb.torproject.org/torbutton.git/blob/HEAD:/src/CHANGELOG">changelog</a> <b>|</b>
-    <a href="https://gitweb.torproject.org/torbutton.git/blob/HEAD:/src/LICENSE">license</a> <b>|</b>
-    <a href="https://gitweb.torproject.org/torbutton.git/blob/HEAD:/src/CREDITS">credits</a> <b>]</b>
+    <a href="https://gitweb.torproject.org/torbutton.git/tree/src/CHANGELOG">changelog</a> <b>|</b>
+    <a href="https://gitweb.torproject.org/torbutton.git/tree/src/LICENSE">license</a> <b>|</b>
+    <a href="https://gitweb.torproject.org/torbutton.git/tree/src/CREDITS">credits</a> <b>]</b>
     
   </div>
   <!-- END MAINCOL -->
diff --git a/eff/en/tor-legal-faq.wml b/eff/en/tor-legal-faq.wml
index 4bc6840..16ac0af 100644
--- a/eff/en/tor-legal-faq.wml
+++ b/eff/en/tor-legal-faq.wml
@@ -154,7 +154,7 @@ relay:</p>
 <li>Set up a reverse DNS name for the IP address that makes clear that
 the computer is an exit relay.</li>
 <li>Set up a notice like <a
-href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/operator-tools/tor-exit-notice.html">this</a>
+href="https://gitweb.torproject.org/tor.git/plain/contrib/operator-tools/tor-exit-notice.html">this</a>
 to explain that you're running an exit relay that's part of the Tor
 network.</li>
 <li>If possible, get an <a href="https://www.arin.net/">ARIN</a>
diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml
index 859ee35..8b9c7fb 100644
--- a/getinvolved/en/volunteer.wml
+++ b/getinvolved/en/volunteer.wml
@@ -892,7 +892,7 @@ meetings around the world.</li>
       href="https://stem.torproject.org/tutorials.html">stem's tutorial
       page</a> demonstrating cross txtorcon/stem usage.</li>
       <li>Expand the txtorcon API to include functionality of <a
-      href="https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/control.py">stem's
+      href="https://gitweb.torproject.org/stem.git/tree/stem/control.py">stem's
       controller</a> that would be of interest to twisted users. All additions
       should include tests!</li>
       <li>Come up with some ideas of your own! We'd love to discuss them with
diff --git a/projects/en/obfsproxy.wml b/projects/en/obfsproxy.wml
index b3b6b98..0a56458 100644
--- a/projects/en/obfsproxy.wml
+++ b/projects/en/obfsproxy.wml
@@ -43,7 +43,7 @@
     <p>
     Even though obfsproxy is a separate application, completely
     independent from tor, it speaks to tor using an <a
-    href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/pt-spec.txt">internal
+    href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">internal
     protocol</a> to minimize necessary end-user configuration.
     </p>
 
diff --git a/projects/en/torbrowser.wml b/projects/en/torbrowser.wml
index c3904e5..337c0e1 100644
--- a/projects/en/torbrowser.wml
+++ b/projects/en/torbrowser.wml
@@ -606,7 +606,7 @@
       document</a>, the <a
       href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/refs/heads/maint-3.6:/Bundle-Data/Docs/ChangeLog.txt">ChangeLog
       for the 3.6 branch</a>, and the <a
-      href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/Bundle-Data/Docs/ChangeLog.txt">ChangeLog
+      href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-Data/Docs/ChangeLog.txt">ChangeLog
       for the alpha branch</a>.
       </p>
       <p><strong><em>How can I make my own bundle?</em></strong>
@@ -616,7 +616,7 @@ to ensure that byte-for-byte reproducible packages can be built from our
 source repository by anyone. To rebuild the bundle, check out the <a
 href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">Tor
 Browser builder repository</a> and see the <a
-href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">README.build</a>
+href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build">README.build</a>
 for instructions. You may also find the <a
 href="https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking">Tor
 Browser Hacking</a> intro document useful for learning about the build system
diff --git a/projects/en/tordnsel.wml b/projects/en/tordnsel.wml
index 3ccd15a..7d661c7 100644
--- a/projects/en/tordnsel.wml
+++ b/projects/en/tordnsel.wml
@@ -27,7 +27,7 @@
     accurate list.</p>
 
     <p>The full background and rationale for TorDNSEL is described in the official
-    <a href="https://gitweb.torproject.org/tordnsel.git/blob/HEAD:/doc/torel-design.txt">design
+    <a href="https://gitweb.torproject.org/tordnsel.git/tree/doc/torel-design.txt">design
     document</a>. The current service only supports the first query type mentioned
     in that document.</p>
 
diff --git a/projects/en/vidalia.wml b/projects/en/vidalia.wml
index 413f509..b8fdb86 100644
--- a/projects/en/vidalia.wml
+++ b/projects/en/vidalia.wml
@@ -97,7 +97,7 @@ href="/dist/vidalia/vidalia-<version-vidalia-alpha>.tar.gz.asc">sig</a>
 
     <p>
     If you intend to start coding already, please read and follow the
-    <a href="https://gitweb.torproject.org/vidalia.git/blob/HEAD:/HACKING">HACKING
+    <a href="https://gitweb.torproject.org/vidalia.git/tree/HACKING">HACKING
     guide</a>.
     If you have a patch for a feature or a bug fix, first check the
     <a href="https://trac.torproject.org/projects/tor/report/27">tickets that





More information about the tor-commits mailing list