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

[PATCH] Minor corrections to notes

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-01-24 18:59:47 CET

Are these corrections correct? Particularly the first one: it seemed to me
that "the target will appear to be added" didn't make sense for "svn log"
commands that trace forwards in time.

- Julian

Minor corrections to some notes.

* notes/authz_policy.txt
  Clarify description of log tracing. Correct some example rev numbers.

* notes/svndiff
  Fix typos.

Index: notes/authz_policy.txt
===================================================================
--- notes/authz_policy.txt (revision 18199)
+++ notes/authz_policy.txt (working copy)
@@ -25,8 +25,9 @@ WHAT USERS SHOULD EXPECT FROM PATH-BASED
    
      * If the target of 'svn log' wanders into unreadable territory,
        then log output will simply stop at the last readable revision.
- The target will appear to be added (without history) in that
- revision.
+ If the log is tracing backwards through time, as the plain
+ "svn log" command does, the target will appear to be added
+ (without history) in that revision.
    
      * If a revision returned by 'svn log' contains a mixture of
        readable/unreadable changed-paths, then the log message is
@@ -72,7 +73,7 @@ WHAT USERS SHOULD EXPECT FROM PATH-BASED
    halts; no further information is retrieved.
    
       Example 1: while 'bar.c' might be perfectly readable in both
- revisions 5 and 20, the 'svn diff' command (above) will return
+ revisions 10 and 28, the 'svn diff' command (above) will return
       error if the file has an unreadable ancestor somewhere between
       those two revisions.
    
Index: notes/svndiff
===================================================================
--- notes/svndiff (revision 18199)
+++ notes/svndiff (working copy)
@@ -47,7 +47,7 @@ byte compose an instruction selector, as
         11 invalid
 
 The remaining six bits of the first byte indicate the length of the
-copy. If those six bytes are all zero, then the length is encoded as
+copy. If those six bits are all zero, then the length is encoded as
 an integer immediately following the first byte of the instruction.
 If the instruction selector is 00 or 01, then the instruction encoding
 continues with an offset encoded as an integer. If the instruction
@@ -55,7 +55,7 @@ selector is 10, then the offset into the
 copy from the new data is always for "the next <length> bytes" after
 the last copy.
 
-A copy from the target view must begin at a location before than the
+A copy from the target view must begin at a location before the
 current position in the target view, but its length may extend past
 the current position. In this case, the target data copied is
 repeated, as happens naturally if the copy is performed byte by byte
@@ -67,7 +67,7 @@ Following are some example instruction e
         00001011 00000000
 
         Copy 64 bytes from offset 128 in target view:
- 01000000 00100000 10000001 00000000
+ 01000000 01000000 10000001 00000000
 
         Copy the next 63 bytes of new data:
         10111111

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 24 19:01:08 2006

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