[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: test patch

From: Zack Brown <zbrown_at_tumblerings.org>
Date: 2002-10-31 05:35:30 CET

On Wed, Oct 30, 2002 at 07:23:15PM -0600, B. W. Fitzpatrick wrote:
>
>
> Zack Brown <zbrown@tumblerings.org> writes:
>
> > I noticed in the guidelines for hacking the docs, we are told to use
> > "Apache HTTP Server" instead of "httpd". Here's a patch to fix some 'httpd'
> > occurrences in the book.
> >
> > Have I submitted this patch properly?
>
> Everything but the log message. :)
>
> Actually, I'm going to hold off on applying this. I went ahead and
> applied it, and it really sounds weird. For now, I'm going to remove
> the directive from doc/book/HACKING until we can decide on what to do.
>
> Sorry for the inconvenience.

You may not like this one either then...

Log Message:
Changed occurrences of "revision control system' to 'version control
system' in the book, as specified in the HACKING file.

Index: doc/book/book/ch01.xml
===================================================================
--- doc/book/book/ch01.xml
+++ doc/book/book/ch01.xml 2002-10-30 20:28:00.000000000 -0800
@@ -26,7 +26,7 @@
     <title>Target audience</title>
 
     <para>The intended audience of this book is anyone who has used a
- revision control system before, although perhaps not Subversion
+ version control system before, although perhaps not Subversion
       or CVS. It assumes that the reader is computer-literate, and
       reasonably comfortable at a Unix command-line.</para>
 
@@ -48,17 +48,17 @@
 
       <title>History of Revision Control</title>
       
- <para>Subversion is a free/open-source <firstterm>revision
+ <para>Subversion is a free/open-source <firstterm>version
           control system</firstterm>. That is, Subversion manages
         files over time. The files are placed into a central
         <firstterm>repository</firstterm>. The repository is much
         like an ordinary file server, except that it remembers every
         change ever made to your files. This allows you to recover
         older versions of your files, or browse the history of how
- your files changed. Many people think of a revision control
+ your files changed. Many people think of a version control
         system as a sort of ``time machine.''</para>
       
- <para>Some revision control systems are also <firstterm>software
+ <para>Some version control systems are also <firstterm>software
           configuration management</firstterm> (SCM) systems. These
         systems are specifically tailored to manage trees of source
         code, and have many features that are specific to software
@@ -79,7 +79,7 @@
         can find more information about CVS at <systemitem
           class="url">http://www.cvshome.org/</systemitem>.</para>
       
- <para>At the time of writing, CVS is the standard Free revision
+ <para>At the time of writing, CVS is the standard Free version
         control system used by the open-source community. It has a
         hard-earned, well-deserved reputation as stable and useful
         software, and has a design that makes it perfect for
Index: doc/book/book/ch03.xml
===================================================================
--- doc/book/book/ch03.xml
+++ doc/book/book/ch03.xml 2002-10-30 20:30:26.000000000 -0800
@@ -272,7 +272,7 @@
         <varlistentry>
           <term>File changes</term>
           <listitem>
- <para>This is the simplest sort of change. Unlike other revision control
+ <para>This is the simplest sort of change. Unlike other version control
               systems, you don't need to tell Subversion that you intend to change a
               file; just do it. Later on, Subversion will be able to automatically
               detect which files have been changed.</para>
@@ -467,7 +467,7 @@
           <listitem>
             <para>The file or directory
               <filename>file_or_dir</filename> indicates that this file
- or directory is not under revision control. You can
+ or directory is not under version control. You can
               silence the question marks by either passing the
               <option>--quiet</option> (<option>-q</option>)
               switch to <command>svn status</command>, or by setting the
@@ -481,7 +481,7 @@
           <term><computeroutput>! file_or_dir</computeroutput></term>
           <listitem>
             <para>The file or directory
- <filename>file_or_dir</filename> is under revision
+ <filename>file_or_dir</filename> is under version
               control but the working copy is missing. This happens
               if the file or directory is removed using a
               non-Subversion command. A quick <command>svn
@@ -495,7 +495,7 @@
           <term><computeroutput>~ file_or_dir</computeroutput></term>
           <listitem>
             <para>The file or directory
- <filename>file_or_dir</filename> is under revision control
+ <filename>file_or_dir</filename> is under version control
            as one kind of object, but what's actually on disk is some
            other kind. For example, Subversion might be expecting a
            file, but the user has removed the file and created a
Index: doc/book/book/ch04.xml
===================================================================
--- doc/book/book/ch04.xml
+++ doc/book/book/ch04.xml 2002-10-30 20:30:58.000000000 -0800
@@ -8,7 +8,7 @@
   <simplesect>
 
     <para>Branches and tags are general concepts common to almost all
- revision control systems. If you're not familiar with these
+ version control systems. If you're not familiar with these
       ideas, you can find a good introductory explanation in Karl
       Fogel's free CVS book: <systemitem
       class="url">http://cvsbook.red-bean.com/cvsbook.html#Branching_Basics</systemitem></para><!--

>
> -Fitz
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>

-- 
Zack Brown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 31 05:36:05 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.