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

SVN -> .svn doc patch

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2001-10-19 19:27:11 CEST

Is this OK? If so I can go ahead and commit it.

Index: ./trunk/doc/programmer/design/client.texi
===================================================================
--- ./trunk/doc/programmer/design/.svn/text-base/client.texi Sat Oct 13 15:34:08 2001
+++ ./trunk/doc/programmer/design/client.texi Thu Oct 18 23:43:15 2001
@@ -45,7 +45,7 @@
 physically, but is not a full specification of working copy layout.
 
 As with CVS, Subversion working copies are simply directory trees with
-special administrative subdirectories, in this case named "SVN" instead
+special administrative subdirectories, in this case named ".svn" instead
 of "CVS":
 
 @example
@@ -54,14 +54,14 @@
                              / | \
                _____________/ | \______________
               / | \
- SVN src doc
+ .svn src doc
         ___/ | \___ /|\ ___/ \___
        | | | / | \ | |
- base ... ... / | \ myproj.texi SVN
+ base ... ... / | \ myproj.texi .svn
                            / | \ ___/ | \___
                       ____/ | \____ | | |
                      | | | base ... ...
- SVN foo.c bar.c |
+ .svn foo.c bar.c |
                 ___/ | \___ |
                | | | |
              base ... ... myproj.texi
@@ -72,7 +72,7 @@
 @end group
 @end example
 
-Each @file{dir/SVN/} directory records the files in @file{dir}, their
+Each @file{dir/.svn/} directory records the files in @file{dir}, their
 revision numbers and property lists, pristine revisions of all the files
 (for client-side delta generation), the repository from which @file{dir}
 came, and any local changes (such as uncommitted adds, deletes, and
@@ -91,7 +91,7 @@
 easier for the user to prune a big, complete tree into a small subtree
 and still have a valid working copy.
 
-The SVN subdir contains:
+The .svn subdir contains:
 
 @itemize @bullet
 
Index: ./trunk/doc/programmer/design/model.texi
===================================================================
--- ./trunk/doc/programmer/design/.svn/text-base/model.texi Sat Oct 13 15:34:08 2001
+++ ./trunk/doc/programmer/design/model.texi Thu Oct 18 23:45:07 2001
@@ -82,13 +82,13 @@
 write/Makefile
       document.c
       search.c
- SVN/
+ .svn/
 @end example
 This working directory is a copy of the repository's @file{/trunk/write}
-directory, with one additional entry --- @file{SVN} --- which holds the
+directory, with one additional entry --- @file{.svn} --- which holds the
 extra information needed by Subversion, as mentioned above.
 
-Suppose you make changes to @file{search.c}. Since the @file{SVN}
+Suppose you make changes to @file{search.c}. Since the @file{.svn}
 directory remembers the file's modification date and original contents,
 Subversion can tell that you've changed the file. However, Subversion
 does not make your changes public until you explicitly tell it to.
@@ -97,8 +97,8 @@
 @example
 $ pwd
 /home/jimb/write
-$ ls
-Makefile SVN/ document.c search.c
+$ ls -a
+.svn/ Makefile document.c search.c
 $ svn commit search.c
 $
 @end example
@@ -120,8 +120,8 @@
 @example
 $ pwd
 /home/felix/write
-$ ls
-Makefile SVN/ document.c search.c
+$ ls -a
+.svn/ Makefile document.c search.c
 $ svn update
 U search.c
 $
@@ -130,7 +130,7 @@
 The output from the @samp{svn update} command indicates that Subversion
 updated the contents of @file{search.c}. Note that Felix didn't need to
 specify which files to update; Subversion uses the information in the
-@file{SVN} directory, and further information in the repository, to
+@file{.svn} directory, and further information in the repository, to
 decide which files need to be brought up to date.
 
 We explain below what happens when both you and Felix make changes to
Index: ./trunk/doc/programmer/design/architecture.texi
===================================================================
--- ./trunk/doc/programmer/design/.svn/text-base/architecture.texi Sat Oct 13 15:34:08 2001
+++ ./trunk/doc/programmer/design/architecture.texi Thu Oct 18 23:42:24 2001
@@ -68,7 +68,7 @@
 The first library provides an API for managing the client's working copy
 of a project. This includes operations like renaming or removal of
 files, patching files, extracting local diffs, and routines for
-maintaining administrative files in the @file{SVN/} directory.
+maintaining administrative files in the @file{.svn/} directory.
 
 The second library provides an API for exchanging information with a
 Subversion repository. This includes the ability to read files, write
Index: ./trunk/doc/user/manual/removals.texi
===================================================================
--- ./trunk/doc/user/manual/.svn/text-base/removals.texi Sat Oct 13 15:34:05 2001
+++ ./trunk/doc/user/manual/removals.texi Fri Oct 19 00:03:11 2001
@@ -94,8 +94,8 @@
 
 After the items are removed from the repository, all tracking
 information about the items is removed from the working copy. In the
-case of a file, its information is removed from @file{SVN/}. In the
-case of a directory, the entire @file{SVN/} administrative area is
+case of a file, its information is removed from @file{.svn/}. In the
+case of a directory, the entire @file{.svn/} administrative area is
 removed, as well as all the administrative areas of its subdirectories.
 
 Note that commit never removes any real working files or directories;
Index: ./trunk/doc/user/manual/adds.texi
===================================================================
--- ./trunk/doc/user/manual/.svn/text-base/adds.texi Sat Oct 13 15:34:05 2001
+++ ./trunk/doc/user/manual/adds.texi Fri Oct 19 00:01:40 2001
@@ -93,7 +93,7 @@
 write/Makefile
       document.c
       search.c
- SVN/
+ .svn/
 @end example
 
 Say we add a new directory @file{fonts} to the working copy:
Index: ./trunk/doc/user/manual/model.texi
===================================================================
--- ./trunk/doc/user/manual/.svn/text-base/model.texi Sat Oct 13 15:34:05 2001
+++ ./trunk/doc/user/manual/model.texi Fri Oct 19 00:02:53 2001
@@ -90,13 +90,13 @@
 write/Makefile
       document.c
       search.c
- SVN/
+ .svn/
 @end example
 This working directory is a copy of the repository's @file{/trunk/write}
-directory, with one additional entry --- @file{SVN} --- which holds the
+directory, with one additional entry --- @file{.svn} --- which holds the
 extra information needed by Subversion, as mentioned above.
 
-Suppose you make changes to @file{search.c}. Since the @file{SVN}
+Suppose you make changes to @file{search.c}. Since the @file{.svn}
 directory remembers the file's modification date and original contents,
 Subversion can tell that you've changed the file. However, Subversion
 does not make your changes public until you explicitly tell it to.
@@ -105,8 +105,8 @@
 @example
 $ pwd
 /home/jimb/write
-$ ls
-Makefile SVN/ document.c search.c
+$ ls -a
+.svn/ Makefile document.c search.c
 $ svn commit search.c
 $
 @end example
@@ -128,8 +128,8 @@
 @example
 $ pwd
 /home/felix/write
-$ ls
-Makefile SVN/ document.c search.c
+$ ls -a
+.svn/ Makefile document.c search.c
 $ svn update
 U search.c
 $
@@ -138,7 +138,7 @@
 The output from the @samp{svn update} command indicates that Subversion
 updated the contents of @file{search.c}. Note that Felix didn't need to
 specify which files to update; Subversion uses the information in the
-@file{SVN} directory, and further information in the repository, to
+@file{.svn} directory, and further information in the repository, to
 decide which files need to be brought up to date.
 
 We explain below what happens when both you and Felix make changes to
Index: ./trunk/doc/user/manual/dirversioning.texi
===================================================================
--- ./trunk/doc/user/manual/.svn/text-base/dirversioning.texi Sat Oct 13 15:34:05 2001
+++ ./trunk/doc/user/manual/dirversioning.texi Fri Oct 19 00:02:01 2001
@@ -91,7 +91,7 @@
 operation only; it should @emph{not} modify your working data!
 
 Another solution is to do the naive thing: after committing the
-deletion of @file{foo}, simply stop tracking the file in the @file{SVN}
+deletion of @file{foo}, simply stop tracking the file in the @file{.svn}
 administrative directory. The client then loses all knowledge of the
 file.
 
@@ -110,7 +110,7 @@
 client.
 
 After deleting @file{foo} and committing, the file is @emph{not} is not
-totally forgotten by the @file{SVN} directory. While the file is no
+totally forgotten by the @file{.svn} directory. While the file is no
 longer considered to be under revision control, it is still secretly
 remembered as having been `deleted'.
 
Index: ./trunk/notes/svn-config-files
===================================================================
--- ./trunk/notes/.svn/text-base/svn-config-files Sat Oct 13 15:35:54 2001
+++ ./trunk/notes/svn-config-files Fri Oct 19 00:06:59 2001
@@ -22,7 +22,7 @@
      * `svn_security', a file which lives in each repository and
         defines ACLs for the plugin_security module
 
- * all files within a working copy's SVN/ administrative directory
+ * all files within a working copy's .svn/ administrative directory
 
 
 This format is parsed by svn_parse(), located in svn_subr/svn_parse.c.

-- 
David Wayne Summers          "Linux: Because reboots are for upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:45 2006

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