D7net
Home
Console
Upload
information
Create File
Create Folder
About
Tools
blackhat.pw
:
/
kunden
/
kunden
/
usr
/
share
/
locale
/
en_GB
/
LC_MESSAGES
/
Filename :
breezy.mo
back
Copy
�� � < \ x y � � � � : � � $ E � & G S Q ( � � J � � 4 . � ` " # � � � Q � f � M + j � � � ! � � � J a J � , � B $ � g � � � � . m � , � / � - , 4 ' a ' � 9 � , � ! � : Q � � � + � + ! ,! >! ( V! 2 ! �! D �! 2 " F" P a" ' �" 1 �" ! # , .# � [# . T$ � �% � 0& � �& � �' � :) � �* � i+ b , y, �- �. � �/ � �0 ' -1 � U1 � 2 � �3 � F4 4 5 I5 R i5 �5 �5 8 �5 ! #6 E6 $ _6 $ �6 b �6 7 % &7 � L7 � �7 ) �8 1 �8 �8 �8 9 � +9 Z : k: Q �: d �: <; F Y; 5 �; ; �; A < T< < r< �< �< �< d = R p= ? �= > % > � @> � �> � �? # W@ " {@ , �@ � �@ � SA T �A � :B ~ C N �C d �C 8 ID @ �D c �D � 'E i �E 2 VF q �F � �F b �G � IH 0 I 1 BI tI ( �I % �I �I J !J ?J 4 WJ m �J > �J 3 9K # mK 2 �K m �K I 2L |L _ �L 7 �L t M � �M � IN } �N 7 YO � �O M yP � �P B PQ 0 �Q C �Q R $R @R ! ^R �R �R �R J �R S : &S ^ aS � �S + cT D �T B �T = U � UU "W CW PW `W qW : �W � �W E �X �X �X S �X ( NY wY J �Y � �Y . �[ �[ ` �[ # ,\ � P\ Q =] f �] �] + ^ ?^ � _^ ! R_ � t_ J a J Ua , �a B �a � b � �b � 4c . d Ed , Rd / d - �d , �d ' e ' 2e 9 Ze , �e ! �e � �e Q sf � �f ig + }g + �g �g �g ( �g 2 (h [h D wh 2 �h �h P i ' [i 1 �i ! �i , �i � j . �j � ,l � �l � `m � Vn � �o � eq � r b �r "s 4t Du � Zv � ,w ' �w � �w � �x � Zz � �z 4 �{ �{ R | e| || 8 �| ! �| �| $ } $ -} b R} �} % �} � �} � �~ ) ) 1 S � � � � � Z �� � Q .� d �� � F � 5 I� ; � A �� �� < � X� y� �� d �� R � ? l� �� % Ä � � � �� � L� # � " $� , G� � t� � �� T �� � � ~ �� N >� d �� 8 � @ +� c l� � Ћ i �� 2 �� q 2� � �� b �� � � 0 �� 1 � � ( =� % f� �� �� ʐ � 4 � m 5� > �� 3 � # � 2 :� m m� I ے %� _ /� 7 �� t Ǔ � <� � � } �� 7 � � :� M "� � p� B �� 0 <� C m� �� ͘ � ! � )� 8� T� J n� �� : ϙ ^ � � i� + � D 8� B }� = �� l � m c � � � ) Z R 4 � = � E B ' C q H � \ � P � � ` � s � � � � O � � � � [ � $ _ � f V � A � Y , � p � � � ( D � n 5 � : � � � � k i � y � X 7 N � ^ � � F W � � e � u ! < d � S > & � g | � @ 2 T L - w � � } ~ U � � . � I * � + � � � % � t 6 / ; K { � 1 v x j h ? � � � � 9 G 0 � � � M � � � z Q � o b a J # r " � ] � � 3 8 brz cp SOURCE... DESTINATION brz info brz info -v brz info -vv brz mv SOURCE... DESTINATION Display information on the format and related locations: Display the above together with extended format information and basic statistics (like the number of files in the working tree and number of revisions in the branch and repository): Display the above together with number of committers to the branch: %d tag updated. %d tags updated. (default) , the header appears corrupt, try passing -r -1 to set the state to the last commit --after cannot be specified with --auto. --dry-run requires --auto. --dry-run will show which files would be added, but not actually add them. --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. --tree and --revision can not be used together :Examples: A warning will be printed when nested trees are encountered, unless they are explicitly ignored. Add specified files or directories. 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. Allow lossy push, i.e. dropping metadata that can't be represented in the target. Any files matching patterns in the ignore list will not be added unless they are explicitly mentioned. Automatically guess renames. Avoid making changes when guessing renames. Backup changed files (default). Before merges are committed, the pending merge tip revisions are shown. To see all pending merge revisions, use the -v option. To skip the display of pending merge information altogether, use the no-pending option or specify a file/directory. Bind new branch to from location. Bisecting, in a nutshell, is a way to find the commit at which some testable change was made, such as the introduction of a bug or feature. By identifying a version which did not have the interesting change and a later version which did, a developer can test for the presence of the change at various points in the history, eventually ending up at the precise commit when the change was first introduced. Branch to pull into, rather than the one containing the working directory. Branch to push from, rather than the one containing the working directory. Branched %d revision. Branched %d revisions. Branches and working trees will also report any missing revisions. By default branch will fail if the target directory exists, but does not already have a control directory. This flag will allow branch to proceed. By default push will fail if the target directory exists, but does not already have a control directory. This flag will allow push to proceed. By default, this command only works on branches that have not diverged. Branches are considered diverged if the destination branch's most recent commit is one that has not been merged (directly or indirectly) into the parent. Cannot use -r with merge directives or bundles Copy a file. Could not copy %s => %s . %s is a directory. Could not copy %s => %s . %s is not versioned\. Could not copy %s => %s: %s is not versioned. Could not copy to %s: %s is not a directory. Could not determine branch to refer to. Create a branch without a working-tree. Create a new branch that is a copy of an existing branch. Create a new checkout of an existing branch. Create a new versioned directory. Create a stacked branch referring to the source branch. The new branch will depend on the availability of the source branch for all operations. Create a stacked branch that references the public location of the parent branch. Create a stacked branch that refers to another branch for the commit history. Only the work not present in the referenced branch is included in the branch created. Created new branch. Created new stacked branch referring to %s. Delete from brz but leave the working copy. Deletion Strategy Display status summary. Do not mark object type using indicator. Do not use a shared repository, even if available. Don't backup changed files. Don't populate the working tree, even for protocols that support it. Don't recursively add the contents of directories. Don't show pending merges. Files cannot be copied between branches. Only files can be copied at the moment. Files cannot be moved between branches. Find an interesting commit using a binary search. Get file contents from this tree. Hard-link working tree files where possible. If BRANCH_LOCATION is omitted, checkout will reconstitute a working tree for the branch found in '.'. This is useful if you have removed the working tree or if it was never created - i.e. if you pushed the branch to its current location using SFTP. 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. If branches have diverged, you can use 'brz merge' to integrate the changes from one into the other. Once one branch has merged, the other should be able to pull it again. If branches have diverged, you can use 'brz push --overwrite' to replace the other branch completely, discarding its unmerged changes. If no arguments are specified, the status of the entire working directory is shown. Otherwise, only the status of the specified files or directories is reported. If a directory is given, status is reported for everything inside that directory. If the TO_LOCATION is omitted, the last component of the BRANCH_LOCATION will be used. In other words, "checkout ../foo/bar" will attempt to create ./bar. If the BRANCH_LOCATION has no / or path separator embedded, the TO_LOCATION is derived from the BRANCH_LOCATION by stripping a leading scheme or drive identifier, if any. For example, "checkout lp:foo-bar" will attempt to create ./foo-bar. If the TO_LOCATION is omitted, the last component of the FROM_LOCATION will be used. In other words, "branch ../foo/bar" will attempt to create ./bar. If the FROM_LOCATION has no / or path separator embedded, the TO_LOCATION is derived from the FROM_LOCATION by stripping a leading scheme or drive identifier, if any. For example, "branch lp:foo-bar" will attempt to create ./foo-bar. If the last argument is a versioned directory, all the other names are copied into it. Otherwise, there must be exactly two arguments and the file is copied to a new name. 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. If the tree's branch is bound to a master branch, brz will also update the branch from the master. If there are any uncommitted changes in the tree, they will be carried across and remain as uncommitted changes after the update. To discard these changes, use 'brz revert'. The uncommitted changes may conflict with the changes brought in by the change in basis revision. 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. If there is no default push location set, the first push 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. If you want to ensure you have the different changes in the other branch, do a merge (see brz help merge) from the other branch, and commit that. After that you will be able to do a push without '--overwrite'. 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. Ignoring files outside view. View is %s 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. 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. 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. In verbose mode, statistical information is included with each report. To see extended statistic information, use a verbosity level of 2 or higher by specifying the verbose option multiple times, e.g. -vv. List the branches available at the current location. Lookup file ids from this tree. Move only the brz identifier of the file, because the file has already been moved. Move or rename a file. New branch bound to %s No error if existing, make parent directories as needed. No new revisions or tags to push. No new revisions to push. No pull location known or specified. No push location known or specified. No push location known or specified. To push to the parent branch (at %s), use 'brz push :parent'. No working tree to remove No working tree, ignoring --show-base Note that --short or -S gives status flags for each item, similar to Subversion's status command. To get output similar to svn -q, use brz status -SV. 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 brz send. Only one path may be specified to --auto. Only remove files that have never been committed. Only show versioned files. Overwrite tags only. Parent of "%s" does not exist. Perform a lightweight checkout. Lightweight checkouts depend on access to the branch for every operation. Normal checkouts can perform common operations like diff and status without such access, and also support local commits. Perform a local pull in a bound branch. Local pulls are not applied to the master branch. Pushed up to revision %d. Recursively scan for branches rather than just looking in the specified location. Refuse to push if there are uncommitted changes in the working tree, --no-strict disables the check. Remove files or directories. Remove the working tree even if it has uncommitted or shelved changes. Remove the working tree from a given branch/checkout. Repository %r does not support access to raw revision texts Revision numbers only make sense for single revisions, not ranges Show current revision number. Show information about a working tree, branch or repository. Show list of renamed files. Show logs of pulled revisions. Show revno of working tree. Since a lightweight checkout is little more than a working tree this will refuse to run against one. Some smart servers or protocols *may* put the working tree in place in the future. Switch the checkout in the current directory to the new branch. Switched to branch: %s Target directory "%s" already exists. The 'dir' argument, if given, must be the location of the root of a working tree to update. By default, the working tree that contains the current working directory is used. 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>. The --verbose option will display the revisions pushed using the log_format configuration option. You can use a different format by overriding it with -Olog_format=<other_format>. The branch {0} has no revision {1}. The file deletion mode to be used. The repository {0} contains no revision {1}. The target branch will not have its working tree populated because this is both expensive, and is not supported on remote file systems. The tree does not appear to be corrupt. You probably want "brz revert" instead. Use "--force" if you are sure you want to reset the working tree. Therefore simply saying 'brz add' will version all files that are currently unknown. This command only works on branches that have not diverged. Branches are considered diverged if the destination branch's most recent commit is one that has not been merged (directly or indirectly) by the source branch. This command uses subcommands to implement the search, each of which changes the state of the bisection. The subcommands are: This command will print the names of all the branches at the current location. This command will show all known locations and formats associated to the tree, branch or repository. This is equal to the number of revisions on this branch. This is equivalent to creating the directory and then adding it. This reports on versioned and unknown files, reporting them grouped by state. Possible states are: This will perform a merge of the destination revision (the tip of the branch, or the specified revision) into the working tree, and then make that revision the basis revision for the working tree. To compare the working directory to a specific revision, pass a single revision to the revision argument. To re-create the working tree, use "brz checkout". To retrieve the branch as of a particular revision, supply the --revision parameter, as in "branch foo/bar -r 5". To retrieve the branch as of a particular revision, supply the --revision parameter, as in "checkout foo/bar -r 5". Note that this will be immediately out of date [so you cannot commit] but it may be useful (i.e. to examine old code.) To see ignored files use 'brz ignored'. For details on the changes to file texts, use 'brz diff'. To see which files have changed in a specific revision, or between two revisions, pass a revision range to the revision argument. This will produce the same results as calling 'brz diff --summarize'. Tree is up to date at revision {0} of branch {1} Turn this branch into a mirror of another branch. Update a mirror of this branch. Update a working tree to a new revision. Updated to revision {0} of branch {1} Use short status indicators. Using saved parent location: %s Using saved push location: %s Write log to this file. You can only supply one of revision_id or --revision You can use this to visit an older revision, or to update a working tree that is out of date from its branch. You cannot remove the working tree from a lightweight checkout You cannot remove the working tree of a remote path You cannot specify a NULL revision. You must supply either --revision or a revision_id Your local commits will now show as pending merges with 'brz status', and can be committed with 'brz commit'. added Versioned in the working copy but not in the previous revision. added %s branch has no revision %s brz update --revision only works for a revision in the branch history brz %s --revision takes exactly one revision identifier brz bisect log [-o file] Output a log of the current bisection to standard output, or to the specified file. brz bisect move -r rev Switch to a different revision manually. Use if the bisect algorithm chooses a revision that is not suitable. Try to move as little as possible. brz bisect no [-r rev] The specified revision (or the current revision, if not given) does not have the characteristic we're looking for, brz bisect replay <logfile> Replay a previously-saved bisect log, forgetting any bisection that might be in progress. brz bisect reset Clear out a bisection in progress. brz bisect run <script> Bisect automatically using <script> to determine 'yes' or 'no'. <script> should exit with: 0 for yes 125 for unknown (like build failed so we could not test) anything else for no brz bisect start Start a bisect, possibly clearing out a previous bisect. brz bisect yes [-r rev] The specified revision (or the current revision, if not given) has the characteristic we're looking for, brz status --revision takes exactly one or two revision specifiers brz update --revision takes exactly one revision brz update can only update a whole tree, not a file or subdirectory can not copy root of branch can not move root of branch checked branch {0} format {1} failed to reset the tree state{0} found error:%s ignored {0} matching "{1}" invalid kind %r specified kind changed File kind has been changed (e.g. from file to directory). missing file argument modified Text has changed since the previous revision. removed Versioned in the previous revision but removed or deleted in the working copy. renamed Path of this file changed from the previous revision; the text may also have changed. This includes files whose parent directory was renamed. skipping {0} (larger than {1} of {2} bytes) to copy multiple files the destination must be a versioned directory to mv multiple files the destination must be a versioned directory unknown Not versioned and not matching an ignore pattern. Project-Id-Version: brz Report-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS> PO-Revision-Date: 2023-09-08 16:30+0000 Last-Translator: FULL NAME <EMAIL@ADDRESS> Language-Team: English (United Kingdom) <en_GB@li.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=n != 1; X-Launchpad-Export-Date: 2023-09-09 07:44+0000 X-Generator: Launchpad (build 32eed776db4e1fe74faaa77122cde19862d565ac) brz cp SOURCE... DESTINATION brz info brz info -v brz info -vv brz mv SOURCE... DESTINATION Display information on the format and related locations: Display the above together with extended format information and basic statistics (like the number of files in the working tree and number of revisions in the branch and repository): Display the above together with number of committers to the branch: %d tag updated. %d tags updated. (default) , the header appears corrupt, try passing -r -1 to set the state to the last commit --after cannot be specified with --auto. --dry-run requires --auto. --dry-run will show which files would be added, but not actually add them. --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. --tree and --revision can not be used together :Examples: A warning will be printed when nested trees are encountered, unless they are explicitly ignored. Add specified files or directories. 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. Allow lossy push, i.e. dropping metadata that can't be represented in the target. Any files matching patterns in the ignore list will not be added unless they are explicitly mentioned. Automatically guess renames. Avoid making changes when guessing renames. Backup changed files (default). Before merges are committed, the pending merge tip revisions are shown. To see all pending merge revisions, use the -v option. To skip the display of pending merge information altogether, use the no-pending option or specify a file/directory. Bind new branch to from location. Bisecting, in a nutshell, is a way to find the commit at which some testable change was made, such as the introduction of a bug or feature. By identifying a version which did not have the interesting change and a later version which did, a developer can test for the presence of the change at various points in the history, eventually ending up at the precise commit when the change was first introduced. Branch to pull into, rather than the one containing the working directory. Branch to push from, rather than the one containing the working directory. Branched %d revision. Branched %d revisions. Branches and working trees will also report any missing revisions. By default branch will fail if the target directory exists, but does not already have a control directory. This flag will allow branch to proceed. By default push will fail if the target directory exists, but does not already have a control directory. This flag will allow push to proceed. By default, this command only works on branches that have not diverged. Branches are considered diverged if the destination branch's most recent commit is one that has not been merged (directly or indirectly) into the parent. Cannot use -r with merge directives or bundles Copy a file. Could not copy %s => %s . %s is a directory. Could not copy %s => %s . %s is not versioned\. Could not copy %s => %s: %s is not versioned. Could not copy to %s: %s is not a directory. Could not determine branch to refer to. Create a branch without a working-tree. Create a new branch that is a copy of an existing branch. Create a new checkout of an existing branch. Create a new versioned directory. Create a stacked branch referring to the source branch. The new branch will depend on the availability of the source branch for all operations. Create a stacked branch that references the public location of the parent branch. Create a stacked branch that refers to another branch for the commit history. Only the work not present in the referenced branch is included in the branch created. Created new branch. Created new stacked branch referring to %s. Delete from brz but leave the working copy. Deletion Strategy Display status summary. Do not mark object type using indicator. Do not use a shared repository, even if available. Don't backup changed files. Don't populate the working tree, even for protocols that support it. Don't recursively add the contents of directories. Don't show pending merges. Files cannot be copied between branches. Only files can be copied at the moment. Files cannot be moved between branches. Find an interesting commit using a binary search. Get file contents from this tree. Hard-link working tree files where possible. If BRANCH_LOCATION is omitted, checkout will reconstitute a working tree for the branch found in '.'. This is useful if you have removed the working tree or if it was never created - i.e. if you pushed the branch to its current location using SFTP. 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. If branches have diverged, you can use 'brz merge' to integrate the changes from one into the other. Once one branch has merged, the other should be able to pull it again. If branches have diverged, you can use 'brz push --overwrite' to replace the other branch completely, discarding its unmerged changes. If no arguments are specified, the status of the entire working directory is shown. Otherwise, only the status of the specified files or directories is reported. If a directory is given, status is reported for everything inside that directory. If the TO_LOCATION is omitted, the last component of the BRANCH_LOCATION will be used. In other words, "checkout ../foo/bar" will attempt to create ./bar. If the BRANCH_LOCATION has no / or path separator embedded, the TO_LOCATION is derived from the BRANCH_LOCATION by stripping a leading scheme or drive identifier, if any. For example, "checkout lp:foo-bar" will attempt to create ./foo-bar. If the TO_LOCATION is omitted, the last component of the FROM_LOCATION will be used. In other words, "branch ../foo/bar" will attempt to create ./bar. If the FROM_LOCATION has no / or path separator embedded, the TO_LOCATION is derived from the FROM_LOCATION by stripping a leading scheme or drive identifier, if any. For example, "branch lp:foo-bar" will attempt to create ./foo-bar. If the last argument is a versioned directory, all the other names are copied into it. Otherwise, there must be exactly two arguments and the file is copied to a new name. 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. If the tree's branch is bound to a master branch, brz will also update the branch from the master. If there are any uncommitted changes in the tree, they will be carried across and remain as uncommitted changes after the update. To discard these changes, use 'brz revert'. The uncommitted changes may conflict with the changes brought in by the change in basis revision. 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. If there is no default push location set, the first push 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. If you want to ensure you have the different changes in the other branch, do a merge (see brz help merge) from the other branch, and commit that. After that you will be able to do a push without '--overwrite'. 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. Ignoring files outside view. View is %s 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. 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. 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. In verbose mode, statistical information is included with each report. To see extended statistic information, use a verbosity level of 2 or higher by specifying the verbose option multiple times, e.g. -vv. List the branches available at the current location. Lookup file ids from this tree. Move only the brz identifier of the file, because the file has already been moved. Move or rename a file. New branch bound to %s No error if existing, make parent directories as needed. No new revisions or tags to push. No new revisions to push. No pull location known or specified. No push location known or specified. No push location known or specified. To push to the parent branch (at %s), use 'brz push :parent'. No working tree to remove No working tree, ignoring --show-base Note that --short or -S gives status flags for each item, similar to Subversion's status command. To get output similar to svn -q, use brz status -SV. 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 brz send. Only one path may be specified to --auto. Only remove files that have never been committed. Only show versioned files. Overwrite tags only. Parent of "%s" does not exist. Perform a lightweight checkout. Lightweight checkouts depend on access to the branch for every operation. Normal checkouts can perform common operations like diff and status without such access, and also support local commits. Perform a local pull in a bound branch. Local pulls are not applied to the master branch. Pushed up to revision %d. Recursively scan for branches rather than just looking in the specified location. Refuse to push if there are uncommitted changes in the working tree, --no-strict disables the check. Remove files or directories. Remove the working tree even if it has uncommitted or shelved changes. Remove the working tree from a given branch/checkout. Repository %r does not support access to raw revision texts Revision numbers only make sense for single revisions, not ranges Show current revision number. Show information about a working tree, branch or repository. Show list of renamed files. Show logs of pulled revisions. Show revno of working tree. Since a lightweight checkout is little more than a working tree this will refuse to run against one. Some smart servers or protocols *may* put the working tree in place in the future. Switch the checkout in the current directory to the new branch. Switched to branch: %s Target directory "%s" already exists. The 'dir' argument, if given, must be the location of the root of a working tree to update. By default, the working tree that contains the current working directory is used. 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>. The --verbose option will display the revisions pushed using the log_format configuration option. You can use a different format by overriding it with -Olog_format=<other_format>. The branch {0} has no revision {1}. The file deletion mode to be used. The repository {0} contains no revision {1}. The target branch will not have its working tree populated because this is both expensive, and is not supported on remote file systems. The tree does not appear to be corrupt. You probably want "brz revert" instead. Use "--force" if you are sure you want to reset the working tree. Therefore simply saying 'brz add' will version all files that are currently unknown. This command only works on branches that have not diverged. Branches are considered diverged if the destination branch's most recent commit is one that has not been merged (directly or indirectly) by the source branch. This command uses subcommands to implement the search, each of which changes the state of the bisection. The subcommands are: This command will print the names of all the branches at the current location. This command will show all known locations and formats associated to the tree, branch or repository. This is equal to the number of revisions on this branch. This is equivalent to creating the directory and then adding it. This reports on versioned and unknown files, reporting them grouped by state. Possible states are: This will perform a merge of the destination revision (the tip of the branch, or the specified revision) into the working tree, and then make that revision the basis revision for the working tree. To compare the working directory to a specific revision, pass a single revision to the revision argument. To re-create the working tree, use "brz checkout". To retrieve the branch as of a particular revision, supply the --revision parameter, as in "branch foo/bar -r 5". To retrieve the branch as of a particular revision, supply the --revision parameter, as in "checkout foo/bar -r 5". Note that this will be immediately out of date [so you cannot commit] but it may be useful (i.e. to examine old code.) To see ignored files use 'brz ignored'. For details on the changes to file texts, use 'brz diff'. To see which files have changed in a specific revision, or between two revisions, pass a revision range to the revision argument. This will produce the same results as calling 'brz diff --summarize'. Tree is up to date at revision {0} of branch {1} Turn this branch into a mirror of another branch. Update a mirror of this branch. Update a working tree to a new revision. Updated to revision {0} of branch {1} Use short status indicators. Using saved parent location: %s Using saved push location: %s Write log to this file. You can only supply one of revision_id or --revision You can use this to visit an older revision, or to update a working tree that is out of date from its branch. You cannot remove the working tree from a lightweight checkout You cannot remove the working tree of a remote path You cannot specify a NULL revision. You must supply either --revision or a revision_id Your local commits will now show as pending merges with 'brz status', and can be committed with 'brz commit'. added Versioned in the working copy but not in the previous revision. added %s branch has no revision %s brz update --revision only works for a revision in the branch history brz %s --revision takes exactly one revision identifier brz bisect log [-o file] Output a log of the current bisection to standard output, or to the specified file. brz bisect move -r rev Switch to a different revision manually. Use if the bisect algorithm chooses a revision that is not suitable. Try to move as little as possible. brz bisect no [-r rev] The specified revision (or the current revision, if not given) does not have the characteristic we're looking for, brz bisect replay <logfile> Replay a previously-saved bisect log, forgetting any bisection that might be in progress. brz bisect reset Clear out a bisection in progress. brz bisect run <script> Bisect automatically using <script> to determine 'yes' or 'no'. <script> should exit with: 0 for yes 125 for unknown (like build failed so we could not test) anything else for no brz bisect start Start a bisect, possibly clearing out a previous bisect. brz bisect yes [-r rev] The specified revision (or the current revision, if not given) has the characteristic we're looking for, brz status --revision takes exactly one or two revision specifiers brz update --revision takes exactly one revision brz update can only update a whole tree, not a file or subdirectory can not copy root of branch can not move root of branch checked branch {0} format {1} failed to reset the tree state{0} found error:%s ignored {0} matching "{1}" invalid kind %r specified kind changed File kind has been changed (e.g. from file to directory). missing file argument modified Text has changed since the previous revision. removed Versioned in the previous revision but removed or deleted in the working copy. renamed Path of this file changed from the previous revision; the text may also have changed. This includes files whose parent directory was renamed. skipping {0} (larger than {1} of {2} bytes) to copy multiple files the destination must be a versioned directory to mv multiple files the destination must be a versioned directory unknown Not versioned and not matching an ignore pattern.