Translations by Anthony Harrington
Anthony Harrington has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1. |
skipping {0} (larger than {1} of {2} bytes)
|
|
| 2012-01-04 |
skipping {0} (larger than {1} of {2} bytes)
|
|
| 2. |
Unstacking
|
|
| 2012-01-04 |
Unstacking
|
|
| 3. |
Pushed up to revision %d.
|
|
| 2012-01-04 |
Pushed up to revision %d.
|
|
| 4. |
%d tag updated.
%d tags updated.
|
|
| 2012-01-04 |
%d tag updated.
%d tags updated.
|
|
| 5. |
No new revisions or tags to push.
|
|
| 2012-01-04 |
No new revisions or tags to push.
|
|
| 6. |
No new revisions to push.
|
|
| 2012-01-04 |
No new revisions to push.
|
|
| 7. |
checked branch {0} format {1}
|
|
| 2012-01-04 |
checked branch {0} format {1}
|
|
| 8. |
found error:%s
|
|
| 2012-01-04 |
found error:%s
|
|
| 9. |
Ignoring files outside view. View is %s
|
|
| 2012-01-04 |
Ignoring files outside view. View is %s
|
|
| 10. |
bzr %s --revision takes exactly one revision identifier
|
|
| 2012-01-04 |
bzr %s --revision takes exactly one revision identifier
|
|
| 17. |
kind changed
File kind has been changed (e.g. from file to directory).
|
|
| 2012-01-19 |
type changed
File type has been changed (e.g. from file to directory).
|
|
| 20. |
To see ignored files use 'bzr ignored'. For details on the
changes to file texts, use 'bzr diff'.
|
|
| 2012-01-19 |
To see ignored files, use 'bzr ignored'. For details on the
changes to file texts, use 'bzr diff'.
|
|
| 32. |
You must supply either --revision or a revision_id
|
|
| 2012-02-14 |
You must supply either --revision or a revision_id
|
|
| 33. |
Repository %r does not support access to raw revision texts
|
|
| 2012-02-14 |
Repository %r does not support access to raw revision texts
|
|
| 34. |
The repository {0} contains no revision {1}.
|
|
| 2012-02-14 |
The repository {0} contains no revision {1}.
|
|
| 36. |
Remove the working tree from a given branch/checkout.
|
|
| 2012-02-14 |
Remove the working tree from a given branch/checkout.
|
|
| 37. |
Since a lightweight checkout is little more than a working tree
this will refuse to run against one.
|
|
| 2012-02-14 |
Since a lightweight checkout is little more than a working tree,
this will refuse to run against one.
|
|
| 38. |
To re-create the working tree, use "bzr checkout".
|
|
| 2012-02-14 |
To re-create the working tree, use "bzr checkout".
|
|
| 40. |
No working tree to remove
|
|
| 2012-02-14 |
No working tree to remove
|
|
| 44. |
, the header appears corrupt, try passing -r -1 to set the state to the last commit
|
|
| 2012-02-14 |
, the header appears corrupt, try passing -r -1 to set the state to the last commit
|
|
| 47. |
This is equal to the number of revisions on this branch.
|
|
| 2012-02-14 |
This is equal to the number of revisions on this branch.
|
|
| 48. |
--tree and --revision can not be used together
|
|
| 2012-02-14 |
--tree and --revision can not be used together
|
|
| 49. |
Revision numbers only make sense for single revisions, not ranges
|
|
| 2013-08-04 |
Revision numbers only make sense for single revisions, not ranges
|
|
| 52. |
In non-recursive mode, all the named items are added, regardless
of whether they were previously ignored. A warning is given if
any of the named files are already versioned.
|
|
| 2012-03-10 |
In non-recursive mode, all the named items are added, regardless
of whether they were previously ignored. A warning is given if
any of the named files are already versioned.
|
|
| 53. |
In recursive mode (the default), files are treated the same way
but the behaviour for directories is different. Directories that
are already versioned do not give a warning. All directories,
whether already versioned or not, are searched for files or
subdirectories that are neither versioned or ignored, and these
are added. This search proceeds recursively into versioned
directories. If no names are given '.' is assumed.
|
|
| 2012-07-28 |
In recursive mode (the default), files are treated the same way
but the behaviour for directories is different. Directories that
are already versioned do not give a warning. All directories,
whether already versioned or not, are searched for files or
subdirectories that are neither versioned or ignored, and these
are added. This search proceeds recursively into versioned
directories. If no names are given '.' is assumed.
|
|
| 54. |
A warning will be printed when nested trees are encountered,
unless they are explicitly ignored.
|
|
| 2012-03-10 |
A warning will be printed when nested trees are encountered,
unless they are explicitly ignored.
|
|
| 56. |
Adding a file whose parent directory is not versioned will
implicitly add the parent, and so on up to the root. This means
you should never need to explicitly add a directory, they'll just
get added when you add a file in the directory.
|
|
| 2012-07-16 |
Adding a file whose parent directory is not versioned will
implicitly add the parent, and so on, up to the root. This means
you should never need to explicitly add a directory, they'll just
get added when you add a file in the directory.
|
|
| 58. |
--file-ids-from will try to use the file ids from the supplied path.
It looks up ids trying to find a matching parent directory with the
same filename, and then by pure path. This option is rarely needed
but can be useful when adding the same logical file into two
branches that will be merged later (without showing the two different
adds as a conflict). It is also useful when merging another project
into a subdirectory of this one.
|
|
| 2012-07-28 |
--file-ids-from will try to use the file ids from the supplied path.
It looks up ids trying to find a matching parent directory with the
same filename, and then by pure path. This option is rarely needed
but can be useful when adding the same logical file into two
branches that will be merged later (without showing the two different
adds as a conflict). It is also useful when merging another project
into a subdirectory of this one.
|
|
| 59. |
Any files matching patterns in the ignore list will not be added
unless they are explicitly mentioned.
|
|
| 2012-03-10 |
Any files matching patterns in the ignore list will not be added
unless they are explicitly mentioned.
|
|
| 60. |
In recursive mode, files larger than the configuration option
add.maximum_file_size will be skipped. Named items are never skipped due
to file size.
|
|
| 2012-02-27 |
In recursive mode, files larger than the configuration option
add.maximum_file_size will be skipped. Named items are never skipped due
to file size.
|
|
| 63. |
ignored {0} matching "{1}"
|
|
| 2012-03-10 |
ignored {0} matching "{1}"
|
|
| 65. |
This is equivalent to creating the directory and then adding it.
|
|
| 2012-03-10 |
This is equivalent to creating the directory and then adding it.
|
|
| 67. |
added %s
|
|
| 2012-03-10 |
added %s
|
|
| 68. |
invalid kind %r specified
|
|
| 2012-08-26 |
invalid kind %r specified
|
|
| 2012-01-19 |
invalid type %r specified
|
|
| 71. |
If the last argument is a versioned directory, all the other names
are moved into it. Otherwise, there must be exactly two arguments
and the file is changed to a new name.
|
|
| 2012-03-10 |
If the last argument is a versioned directory, all the other names
are moved into it. Otherwise, there must be exactly two arguments
and the file is changed to a new name.
|
|
| 72. |
If OLDNAME does not exist on the filesystem but is versioned and
NEWNAME does exist on the filesystem but is not versioned, mv
assumes that the file has been manually moved and only updates
its internal inventory to reflect that change.
The same is valid when moving many SOURCE files to a DESTINATION.
|
|
| 2012-03-10 |
If OLDNAME does not exist on the filesystem but is versioned and
NEWNAME does exist on the filesystem but is not versioned, mv
assumes that the file has been manually moved and only updates
its internal inventory to reflect that change.
The same is valid when moving many SOURCE files to a DESTINATION.
|
|
| 74. |
Move only the bzr identifier of the file, because the file has already been moved.
|
|
| 2012-03-10 |
Move only the bzr identifier of the file, because the file has already been moved.
|
|
| 85. |
If branches have diverged, you can use 'bzr merge' to integrate the changes
from one into the other. Once one branch has merged, the other should
be able to pull it again.
|
|
| 2012-07-16 |
If branches have diverged, you can use 'bzr merge' to integrate the changes
from one into the other. Once one branch has merged, the other should
be able to pull it again.
|
|
| 86. |
If you want to replace your local changes and just want your branch to
match the remote one, use pull --overwrite. This will work even if the two
branches have diverged.
|
|
| 2012-07-16 |
If you want to replace your local changes and just want your branch to
match the remote one, use pull --overwrite. This will work even if the two
branches have diverged.
|
|
| 87. |
If there is no default location set, the first pull will set it (use
--no-remember to avoid setting it). After that, you can omit the
location to use the default. To change the default, use --remember. The
value will only be saved if the remote location can be accessed.
|
|
| 2012-07-28 |
If there is no default location set, the first pull will set it (use
--no-remember to avoid setting it). After that, you can omit the
location to use the default. To change the default, use --remember. The
value will only be saved if the remote location can be accessed.
|
|
| 88. |
The --verbose option will display the revisions pulled using the log_format
configuration option. You can use a different format by overriding it with
-Olog_format=<other_format>.
|
|
| 2012-07-28 |
The --verbose option will display the revisions pulled using the log_format
configuration option. You can use a different format by overriding it with
-Olog_format=<other_format>.
|
|
| 89. |
Note: The location can be specified either in the form of a branch,
or in the form of a path to a file containing a merge directive generated
with bzr send.
|
|
| 2012-07-28 |
Note: The location can be specified either in the form of a branch,
or in the form of a path to a file containing a merge directive generated
with bzr send.
|
|
| 90. |
Show logs of pulled revisions.
|
|
| 2012-07-28 |
Show logs of pulled revisions.
|
|
| 91. |
Branch to pull into, rather than the one containing the working directory.
|
|
| 2012-07-28 |
Branch to pull into, rather than the one containing the working directory.
|
|
| 92. |
Perform a local pull in a bound branch. Local pulls are not applied to the master branch.
|
|
| 2012-08-05 |
Perform a local pull in a bound branch. Local pulls are not applied to the master branch.
|
|
| 93. |
No working tree, ignoring --show-base
|
|
| 2013-08-04 |
No working tree, ignoring --show-base
|
|
| 94. |
No pull location known or specified.
|
|
| 2012-07-28 |
No pull location known or specified.
|
|
| 95. |
Using saved parent location: %s
|
|
| 2012-07-28 |
Using saved parent location: %s
|
|
| 96. |
Cannot use -r with merge directives or bundles
|
|
| 2012-08-05 |
Cannot use -r with merge directives or bundles
|
|
