Browsing French translation

829.

Url '%s' is not in repository '%s'

832.

No lock on path '%s'; repository is unchanged

1105.

APR doesn't support threads

1501.

Invalid conflict file '%s' for '%s'

1502.

Invalid property reject file '%s' for '%s'

1739.

Show the log messages for a set of revision(s) and/or path(s).
usage: 1. log [PATH][@REV]
2. log URL[@REV] [PATH...]

1. Print the log messages for the URL corresponding to PATH
(default: '.'). If specified, REV is the revision in which the
URL is first looked up, and the default revision range is REV:1.
If REV is not specified, the default revision range is BASE:1,
since the URL might not exist in the HEAD revision.

2. Print the log messages for the PATHs (default: '.') under URL.
If specified, REV is the revision in which the URL is first
looked up, and the default revision range is REV:1; otherwise,
the URL is looked up in HEAD, and the default revision range is
HEAD:1.

Multiple '-c' or '-r' options may be specified (but not a
combination of '-c' and '-r' options), and mixing of forward and
reverse ranges is allowed.

With -v, also print all affected paths with each log message.
With -q, don't print the log message body itself (note that this is
compatible with -v).

Each log message is printed just once, even if more than one of the
affected paths for that revision were explicitly requested. Logs
follow copy history by default. Use --stop-on-copy to disable this
behavior, which can be useful for determining branchpoints.

The --depth option is only valid in combination with the --diff option
and limits the scope of the displayed diff to the specified depth.

Examples:
svn log
svn log foo.c
svn log bar.c@42
svn log http://www.example.com/repo/project/foo.c
svn log http://www.example.com/repo/project foo.c bar.c
svn log http://www.example.com/repo/project@50 foo.c bar.c

1743.

Display merge-related information.
usage: mergeinfo SOURCE[@REV] [TARGET[@REV]]

Display information related to merges (or potential merges) between
SOURCE and TARGET (default: '.'). Display the type of information
specified by the --show-revs option. If --show-revs isn't passed,
it defaults to --show-revs='merged'.

The depth can be 'empty' or 'infinity'; the default is 'empty'.

1746.

Apply a patch to a working copy.
usage: patch PATCHFILE [WCPATH]

Apply a unidiff patch in PATCHFILE to the working copy WCPATH.
If WCPATH is omitted, '.' is assumed.

A unidiff patch suitable for application to a working copy can be
produced with the 'svn diff' command or third-party diffing tools.
Any non-unidiff content of PATCHFILE is ignored.

Changes listed in the patch will either be applied or rejected.
If a change does not match at its exact line offset, it may be applied
earlier or later in the file if a match is found elsewhere for the
surrounding lines of context provided by the patch.
A change may also be applied with fuzz, which means that one
or more lines of context are ignored when matching the change.
If no matching context can be found for a change, the change conflicts
and will be written to a reject file with the extension .svnpatch.rej.

For each patched file a line will be printed with characters reporting
the action taken. These characters have the following meaning:

A Added
D Deleted
U Updated
C Conflict
G Merged (with local uncommitted changes)

Changes applied with an offset or fuzz are reported on lines starting
with the '>' symbol. You should review such changes carefully.

If the patch removes all content from a file, that file is scheduled
for deletion. If the patch creates a new file, that file is scheduled
for addition. Use 'svn revert' to undo deletions and additions you
do not agree with.

Hint: If the patch file was created with Subversion, it will contain
the number of a revision N the patch will cleanly apply to
(look for lines like "--- foo/bar.txt (revision N)").
To avoid rejects, first update to the revision N using
'svn update -r N', apply the patch, and then update back to the
HEAD revision. This way, conflicts can be resolved interactively.