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

svn help export is ambiguous

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-07-20 00:02:28 CEST

Hi folks,

The help output for svn export (v1.2.0) states:
2. <snip> ...
  If REV is not specified, all local changes will be preserved,
  but files not under version control will not be copied.

This implies that if REV _is_ specified then files not under version
control could be exported, which is of course nonsense. The attached
patch splits this into 2 sentences.

Also in the export command line help, on my Windows 2000 PC, lines of
exactly 80 characters are followed by a spurious empty line so the
--native-eol switch description is split. If you could restrict output
to 79 columns it should work on any standard terminal. Maybe only
Windows has this problem, but using all 80 chars could be construed as a
(literal) edge case.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org

[[[
* subversion/clients/cmdline/main.c:
  Clarify the help text export of a working copy.
]]]

Index: main.c
===================================================================
--- main.c (revision 15370)
+++ main.c (working copy)
@@ -330,7 +330,7 @@
        "PATH1 is used\n"
        " for the local directory name. If REV is not specified,"
        " all local\n"
- " changes will be preserved, but files not under version "
+ " changes will be preserved. Files not under version "
        "control will\n"
        " not be copied.\n"
        "\n"

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 20 00:02:14 2005

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.