Translations by Joel Pickett

Joel Pickett has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.

150 of 1640 results
~
post-commit hook failed with no error message
2011-12-13
post-commit hook failed with no error message
~
post-commit FS processing had error '%s'.
2011-12-13
post-commit FS processing had error '%s'.
~
svn: warning: The depth of this commit is '%s', but copied directories will regardless be committed with depth '%s'. You must remove unwanted children of those directories in a separate commit.
2011-12-13
svn: warning: The depth of this commit is '%s', but copied directories will regardless be committed with depth '%s'. You must remove unwanted children of those directories in a separate commit.
~
access to '%s' forbidden
2011-12-13
access to '%s' forbidden
~
Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.apache.org/ This product includes software developed by CollabNet (http://www.Collab.Net/).
2011-12-13
Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.apache.org/ This product includes software developed by CollabNet (http://www.Collab.Net/).
~
post commit FS processing had error '%s' and %s
2011-12-13
post commit FS processing had error '%s' and %s
~
'%s' is a directory. Please move it out of the way and try again
2011-12-13
'%s' is a directory. Please move it out of the way and try again
~
usage: svnsync synchronize DEST_URL Transfer all pending revisions to the destination from the source with which it was initialized.
2011-11-19
usage: svnsync synchronize DEST_URL Transfer all pending revisions to the destination from the source with which it was initialised.
~
usage: svnsync initialize DEST_URL SOURCE_URL Initialize a destination repository for synchronization from another repository. The destination URL must point to the root of a repository with no committed revisions. The destination repository must allow revision property changes. If the source URL is not the root of a repository, only the specified part of the repository will be synchronized. You should not commit to, or make revision property changes in, the destination repository by any method other than 'svnsync'. In other words, the destination repository should be a read-only mirror of the source repository.
2011-11-19
usage: svnsync initialize DEST_URL SOURCE_URL Initialise a destination repository for synchronisation from another repository. The destination URL must point to the root of a repository with no committed revisions. The destination repository must allow revision property changes. If the source URL is not the root of a repository, only the specified part of the repository will be synchronized. You should not commit to, or make revision property changes in, the destination repository by any method other than 'svnsync'. In other words, the destination repository should be a read-only mirror of the source repository.
~
usage: svnsync copy-revprops DEST_URL [REV[:REV2]] Copy the revision properties in a given range of revisions to the destination from the source with which it was initialized. If REV and REV2 are provided, copy properties for the revisions specified by that range, inclusively. If only REV is provided, copy properties for that revision alone. If REV is not provided, copy properties for all revisions previously transferred to the destination. REV and REV2 must be revisions which were previously transferred to the destination. You may use "HEAD" for either revision to mean "the last revision transferred".
2011-11-19
usage: svnsync copy-revprops DEST_URL [REV[:REV2]] Copy the revision properties in a given range of revisions to the destination from the source with which it was initialised. If REV and REV2 are provided, copy properties for the revisions specified by that range, inclusively. If only REV is provided, copy properties for that revision alone. If REV is not provided, copy properties for all revisions previously transferred to the destination. REV and REV2 must be revisions which were previously transferred to the destination. You may use "HEAD" for either revision to mean "the last revision transferred".
~
Can't get local hostname
2011-11-19
Can't get local hostname
~
Cannot initialize a repository with content in it
2011-11-19
Cannot initialise a repository with content in it
~
'%s' not versioned, and not exported
2011-11-19
'%s' not versioned, and not exported
~
exported%s
2011-11-19
exported%s
~
'%s' is not a valid revision range
2011-11-19
'%s' is not a valid revision range
~
usage: svnversion [OPTIONS] [WC_PATH [TRAIL_URL]] Produce a compact 'version number' for the working copy path WC_PATH. TRAIL_URL is the trailing portion of the URL used to determine if WC_PATH itself is switched (detection of switches within WC_PATH does not rely on TRAIL_URL). The version number is written to standard output. For example: $ svnversion . /repos/svn/trunk 4168 The version number will be a single number if the working copy is single revision, unmodified, not switched and with an URL that matches the TRAIL_URL argument. If the working copy is unusual the version number will be more complex: 4123:4168 mixed revision working copy 4168M modified working copy 4123S switched working copy 4123P partial working copy, from a sparse checkout 4123:4168MS mixed revision, modified, switched working copy If invoked on a directory that is not a working copy, an exported directory say, the program will output 'exported'. If invoked without arguments WC_PATH will be the current directory. Valid options:
2011-11-19
usage: svnversion [OPTIONS] [WC_PATH [TRAIL_URL]] Produce a compact 'version number' for the working copy path WC_PATH. TRAIL_URL is the trailing portion of the URL used to determine if WC_PATH itself is switched (detection of switches within WC_PATH does not rely on TRAIL_URL). The version number is written to standard output. For example: $ svnversion . /repos/svn/trunk 4168 The version number will be a single number if the working copy is single revision, unmodified, not switched and with an URL that matches the TRAIL_URL argument. If the working copy is unusual the version number will be more complex: 4123:4168 mixed revision working copy 4168M modified working copy 4123S switched working copy 4123P partial working copy, from a sparse checkout 4123:4168MS mixed revision, modified, switched working copy If invoked on a directory that is not a working copy, an exported directory say, the program will output 'exported'. If invoked without arguments WC_PATH will be the current directory. Valid options:
~
Display merge-related information. usage: mergeinfo SOURCE[@REV] [TARGET[@REV]] Display information related to merges (or potential merges) between SOURCE and TARGET (default: '.'). If the --show-revs option is not provided, display revisions which have been merged from SOURCE to TARGET; otherwise, display the type of information specified by the --show-revs option.
2011-07-20
Display merge-related information. usage: mergeinfo SOURCE[@REV] [TARGET[@REV]] Display information related to merges (or potential merges) between SOURCE and TARGET (default: '.'). If the --show-revs option is not provided, display revisions which have been merged from SOURCE to TARGET; otherwise, display the type of information specified by the --show-revs option.
~
specify automatic conflict resolution source ('base', 'working', 'mine-conflict', 'theirs-conflict', 'mine-full', 'theirs-full')
2011-07-20
specify automatic conflict resolution source ('base', 'working', 'mine-conflict', 'theirs-conflict', 'mine-full', 'theirs-full')
~
Show the log messages for a set of revision(s) and/or file(s). usage: 1. log [PATH] 2. log URL[@REV] [PATH...] 1. Print the log messages for a local PATH (default: '.'). The default revision range is BASE:1. 2. Print the log messages for the PATHs (default: '.') under URL. If specified, REV determines in which revision 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. Examples: svn log svn log foo.c svn log http://www.example.com/repo/project/foo.c svn log http://www.example.com/repo/project foo.c bar.c
2011-07-20
Show the log messages for a set of revision(s) and/or file(s). usage: 1. log [PATH] 2. log URL[@REV] [PATH...] 1. Print the log messages for a local PATH (default: '.'). The default revision range is BASE:1. 2. Print the log messages for the PATHs (default: '.') under URL. If specified, REV determines in which revision 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 behaviour, which can be useful for determining branchpoints. Examples: svn log svn log foo.c svn log http://www.example.com/repo/project/foo.c svn log http://www.example.com/repo/project foo.c bar.c
~
Apply the differences between two sources to a working copy path. usage: 1. merge sourceURL1[@N] sourceURL2[@M] [WCPATH] 2. merge sourceWCPATH1@N sourceWCPATH2@M [WCPATH] 3. merge [-c M[,N...] | -r N:M ...] SOURCE[@REV] [WCPATH] 1. In the first form, the source URLs are specified at revisions N and M. These are the two sources to be compared. The revisions default to HEAD if omitted. 2. In the second form, the URLs corresponding to the source working copy paths define the sources to be compared. The revisions must be specified. 3. In the third form, SOURCE can be either a URL or a working copy path (in which case its corresponding URL is used). SOURCE (in revision REV) is compared as it existed between revisions N and M for each revision range provided. If REV is not specified, HEAD is assumed. '-c M' is equivalent to '-r <M-1>:M', and '-c -M' does the reverse: '-r M:<M-1>'. If no revision ranges are specified, the default range of 0:REV is used. Multiple '-c' and/or '-r' options may be specified, and mixing of forward and reverse ranges is allowed. WCPATH is the working copy path that will receive the changes. If WCPATH is omitted, a default value of '.' is assumed, unless the sources have identical basenames that match a file within '.': in which case, the differences will be applied to that file. NOTE: Subversion will only record metadata to track the merge if the two sources are on the same line of history -- if the first source is an ancestor of the second, or vice-versa. This is guaranteed to be the case when using the third form listed above. The --ignore-ancestry option overrides this, forcing Subversion to regard the sources as unrelated and not to track the merge.
2011-07-20
Apply the differences between two sources to a working copy path. usage: 1. merge sourceURL1[@N] sourceURL2[@M] [WCPATH] 2. merge sourceWCPATH1@N sourceWCPATH2@M [WCPATH] 3. merge [-c M[,N...] | -r N:M ...] SOURCE[@REV] [WCPATH] 1. In the first form, the source URLs are specified at revisions N and M. These are the two sources to be compared. The revisions default to HEAD if omitted. 2. In the second form, the URLs corresponding to the source working copy paths define the sources to be compared. The revisions must be specified. 3. In the third form, SOURCE can be either a URL or a working copy path (in which case its corresponding URL is used). SOURCE (in revision REV) is compared as it existed between revisions N and M for each revision range provided. If REV is not specified, HEAD is assumed. '-c M' is equivalent to '-r <M-1>:M', and '-c -M' does the reverse: '-r M:<M-1>'. If no revision ranges are specified, the default range of 0:REV is used. Multiple '-c' and/or '-r' options may be specified, and mixing of forward and reverse ranges is allowed. WCPATH is the working copy path that will receive the changes. If WCPATH is omitted, a default value of '.' is assumed, unless the sources have identical basenames that match a file within '.': in which case, the differences will be applied to that file. NOTE: Subversion will only record metadata to track the merge if the two sources are on the same line of history -- if the first source is an ancestor of the second, or vice-versa. This is guaranteed to be the case when using the third form listed above. The --ignore-ancestry option overrides this, forcing Subversion to regard the sources as unrelated and not to track the merge.
~
Restore pristine working copy file (undo most local edits). usage: revert PATH... Note: this subcommand does not require network access, and resolves any conflicted states. However, it does not restore removed directories.
2011-07-20
Restore pristine working copy file (undo most local edits). usage: revert PATH... Note: this subcommand does not require network access, and resolves any conflicted states. However, it does not restore removed directories.
~
Set the value of a property on files, dirs, or revisions. usage: 1. propset PROPNAME PROPVAL PATH... 2. propset PROPNAME --revprop -r REV PROPVAL [TARGET] 1. Changes a versioned file or directory property in a working copy. 2. Changes an unversioned property on a repository revision. (TARGET only determines which repository to access.) The value may be provided with the --file option instead of PROPVAL. Note: svn recognizes the following special versioned properties but will store any arbitrary properties set: svn:ignore - A newline separated list of file glob patterns to ignore. svn:keywords - Keywords to be expanded. Valid keywords are: URL, HeadURL - The URL for the head version of the object. Author, LastChangedBy - The last person to modify the file. Date, LastChangedDate - The date/time the object was last modified. Rev, Revision, - The last revision the object changed. LastChangedRevision Id - A compressed summary of the previous 4 keywords. Header - Similar to Id but includes the full URL. svn:executable - If present, make the file executable. Use 'svn propdel svn:executable PATH...' to clear. svn:eol-style - One of 'native', 'LF', 'CR', 'CRLF'. svn:mime-type - The mimetype of the file. Used to determine whether to merge the file, and how to serve it from Apache. A mimetype beginning with 'text/' (or an absent mimetype) is treated as text. Anything else is treated as binary. svn:externals - A newline separated list of module specifiers, each of which consists of a relative directory path, optional revision flags and an URL. The ordering of the three elements implements different behavior. Subversion 1.4 and earlier only support the following formats and the URLs cannot have peg revisions: foo http://example.com/repos/zig foo/bar -r 1234 http://example.com/repos/zag Subversion 1.5 and greater support the above formats and the following formats where the URLs may have peg revisions: http://example.com/repos/zig foo -r 1234 http://example.com/repos/zig foo/bar Relative URLs are supported in Subversion 1.5 and greater for all above formats and are indicated by starting the URL with one of the following strings ../ to the parent directory of the extracted external ^/ to the repository root // to the scheme / to the server root The ambiguous format 'relative_path relative_path' is taken as 'relative_url relative_path' with peg revision support. svn:needs-lock - If present, indicates that the file should be locked before it is modified. Makes the working copy file read-only when it is not locked. Use 'svn propdel svn:needs-lock PATH...' to clear. The svn:keywords, svn:executable, svn:eol-style, svn:mime-type and svn:needs-lock properties cannot be set on a directory. A non-recursive attempt will fail, and a recursive attempt will set the property only on the file children of the directory.
2011-07-20
Set the value of a property on files, dirs, or revisions. usage: 1. propset PROPNAME PROPVAL PATH... 2. propset PROPNAME --revprop -r REV PROPVAL [TARGET] 1. Changes a versioned file or directory property in a working copy. 2. Changes an unversioned property on a repository revision. (TARGET only determines which repository to access.) The value may be provided with the --file option instead of PROPVAL. Note: svn recognises the following special versioned properties but will store any arbitrary properties set: svn:ignore - A newline separated list of file glob patterns to ignore. svn:keywords - Keywords to be expanded. Valid keywords are: URL, HeadURL - The URL for the head version of the object. Author, LastChangedBy - The last person to modify the file. Date, LastChangedDate - The date/time the object was last modified. Rev, Revision, - The last revision the object changed. LastChangedRevision Id - A compressed summary of the previous 4 keywords. Header - Similar to Id but includes the full URL. svn:executable - If present, make the file executable. Use 'svn propdel svn:executable PATH...' to clear. svn:eol-style - One of 'native', 'LF', 'CR', 'CRLF'. svn:mime-type - The mimetype of the file. Used to determine whether to merge the file, and how to serve it from Apache. A mimetype beginning with 'text/' (or an absent mimetype) is treated as text. Anything else is treated as binary. svn:externals - A newline separated list of module specifiers, each of which consists of a relative directory path, optional revision flags and an URL. The ordering of the three elements implements different behaviour. Subversion 1.4 and earlier only support the following formats and the URLs cannot have peg revisions: foo http://example.com/repos/zig foo/bar -r 1234 http://example.com/repos/zag Subversion 1.5 and greater support the above formats and the following formats where the URLs may have peg revisions: http://example.com/repos/zig foo -r 1234 http://example.com/repos/zig foo/bar Relative URLs are supported in Subversion 1.5 and greater for all above formats and are indicated by starting the URL with one of the following strings ../ to the parent directory of the extracted external ^/ to the repository root // to the scheme / to the server root The ambiguous format 'relative_path relative_path' is taken as 'relative_url relative_path' with peg revision support. svn:needs-lock - If present, indicates that the file should be locked before it is modified. Makes the working copy file read-only when it is not locked. Use 'svn propdel svn:needs-lock PATH...' to clear. The svn:keywords, svn:executable, svn:eol-style, svn:mime-type and svn:needs-lock properties cannot be set on a directory. A non-recursive attempt will fail, and a recursive attempt will set the property only on the file children of the directory.
~
lump-merge all of source URL's unmerged changes
2011-07-20
lump-merge all of source URL's unmerged changes
~
set user configuration option in the format: FILE:SECTION:OPTION=[VALUE] For example: servers:global:http-library=serf
2011-07-20
set user configuration option in the format: FILE:SECTION:OPTION=[VALUE] For example: servers:global:http-library=serf
~
Recursively clean up the working copy, removing locks, resuming unfinished operations, etc. usage: cleanup [PATH...]
2011-07-20
Recursively clean up the working copy, removing locks, resuming unfinished operations, etc. usage: cleanup [PATH...]
~
operate only on members of changelist ARG [aliases: --cl]
2011-07-20
operate only on members of changelist ARG [aliases: --cl]
~
mark revisions as merged (use with -r)
2011-07-20
mark revisions as merged (use with -r)
~
accept unknown SSL server certificates without prompting (but only with '--non-interactive')
2011-07-20
accept unknown SSL server certificates without prompting (but only with '--non-interactive')
~
Associate (or dissociate) changelist CLNAME with the named files. usage: 1. changelist CLNAME TARGET... 2. changelist --remove TARGET...
2011-07-20
Associate (or dissociate) changelist CLNAME with the named files. usage: 1. changelist CLNAME TARGET... 2. changelist --remove TARGET...
~
specify automatic conflict resolution action ('postpone', 'base', 'mine-conflict', 'theirs-conflict', 'mine-full', 'theirs-full', 'edit', 'launch')
2011-07-20
specify automatic conflict resolution action ('postpone', 'base', 'mine-conflict', 'theirs-conflict', 'mine-full', 'theirs-full', 'edit', 'launch')
~
Remove files and directories from version control. usage: 1. delete PATH... 2. delete URL... 1. Each item specified by a PATH is scheduled for deletion upon the next commit. Files, and directories that have not been committed, are immediately removed from the working copy unless the --keep-local option is given. PATHs that are, or contain, unversioned or modified items will not be removed unless the --force option is given. 2. Each item specified by a URL is deleted from the repository via an immediate commit.
2011-07-20
Remove files and directories from version control. usage: 1. delete PATH... 2. delete URL... 1. Each item specified by a PATH is scheduled for deletion upon the next commit. Files, and directories that have not been committed, are immediately removed from the working copy unless the --keep-local option is given. PATHs that are, or contain, unversioned or modified items will not be removed unless the --force option is given. 2. Each item specified by a URL is deleted from the repository via an immediate commit.
~
set new working copy depth to ARG ('exclude', 'empty', 'files', 'immediates', or 'infinity')
2011-07-20
set new working copy depth to ARG ('exclude', 'empty', 'files', 'immediates', or 'infinity')
~
%s: (Not a valid URL)
2011-07-20
%s: (Not a valid URL)
~
limit operation by depth ARG ('empty', 'files', 'immediates', or 'infinity')
2011-07-20
limit operation by depth ARG ('empty', 'files', 'immediates', or 'infinity')
~
%s: (Not a versioned resource)
2011-07-20
%s: (Not a versioned resource)
~
Only relative paths can be specified after a URL
2011-07-20
Only relative paths can be specified after a URL
~
Subversion is a tool for version control. For additional information, see http://subversion.tigris.org/
2011-07-20
Subversion is a tool for version control. For additional information, see http://subversion.tigris.org/
~
Target lists to diff may not contain both working copy paths and URLs
2011-07-20
Target lists to diff may not contain both working copy paths and URLs
~
Checksum mismatch for '%s'; expected: '%s', recorded: '%s'
2011-07-20
Checksum mismatch for '%s'; expected: '%s', recorded: '%s'
~
Cannot find a URL for '%s'
2011-07-20
Cannot find a URL for '%s'
~
Unable to make any directories
2011-07-20
Unable to make any directories
~
Destination directory of add-with-history is missing a URL
2011-07-20
Destination directory of add-with-history is missing a URL
~
File '%s' in directory '%s' is not a versioned resource
2011-07-20
File '%s' in directory '%s' is not a versioned resource
~
Destination URLs are broken
2011-07-20
Destination URLs are broken
~
No fetch_func supplied to update_editor
2011-07-20
No fetch_func supplied to update_editor
~
Failed to add file '%s': a non-file object of the same name already exists
2011-07-20
Failed to add file '%s': a non-file object of the same name already exists
~
Failed to add file '%s': an unversioned file of the same name already exists
2011-07-20
Failed to add file '%s': an unversioned file of the same name already exists
~
Failed to add directory '%s': copyfrom arguments not yet supported
2011-07-20
Failed to add directory '%s': copyfrom arguments not yet supported
~
UUID mismatch: existing file '%s' was checked out from a different repository
2011-07-20
UUID mismatch: existing file '%s' was checked out from a different repository
~
'%s' has no ancestry information
2011-07-20
'%s' has no ancestry information