Translations by Wellington Oliveira

Since a lightweight checkout is little more than a working tree this will refuse to run against one.

No error if existing, make parent directories as needed.

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.

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.

Your local commits will now show as pending merges with 'bzr status', and can be committed with 'bzr commit'.

This branch format cannot be set to append-revisions-only. Try --default.

Make a lightweight checkout elsewhere::

"bzr diff -p1" is equivalent to "bzr diff --prefix old/:new/", and produces patches suitable for "patch -p1".

Show just the differences for file NEWS::

Show the differences in working tree xxx for file NEWS::

Show the differences from branch xxx to this working tree:

Show the differences between two branches for file NEWS::

bzr diff --old xxx --new yyy NEWS

bzr diff --prefix old/:new/ Show the differences using a custom diff program with options:: bzr diff --using /usr/bin/diff --diff-options -wu

bzr log log the current branch bzr log foo.py log a file in its branch bzr log http://server/branch log a branch on a server

The following options can be used to control what information is displayed::

Historical context is also important when interpreting pathnames of renamed files/directories. Consider the following example:

* revision 1: add tutorial.txt * revision 2: modify tutorial.txt * revision 3: rename tutorial.txt to guide.txt; add tutorial.txt

* ``bzr log guide.txt`` will log the file added in revision 1

* ``bzr log tutorial.txt`` will log the new file added in revision 3

* ``bzr log -r2 -p tutorial.txt`` will show the changes made to the original file in revision 2.

* ``bzr log -r2 -p guide.txt`` will display an error message as there was no file called guide.txt in revision 2.

Renames are always followed by log. By design, there is no need to explicitly ask for this (and no way to stop logging a file back until it was last renamed).

You may find it useful to add the aliases below to ``bazaar.conf``::

If you are interested in looking deeper into a particular merge X, use ``bzr log -n0 -rX``.

Limit the output to the first N revisions.

Show merged revisions like --levels 0 does.

Do not report commits with more than one parent.

Show revisions whose properties match this expression.

Show revisions whose message matches this expression.

Show revisions whose authors match this expression.

Show revisions whose bugs match this expression.

--exclude-common-ancestry requires -r with two revisions

Path unknown at end or start of revision range: %s

bzr %s --revision takes one or two values.

Patterns prefixed with '!!' act as regular ignore patterns, but have precedence over the '!' exception patterns.

* Ignore patterns starting with "#" act as comments in the ignore file. To ignore patterns that begin with that character, use the "RE:" prefix.

Display the default ignore rules that bzr uses.

ignore requires at least one NAME_PATTERN or --default-rules.

Invalid ignore pattern found. %s

Invalid ignore patterns found. %s

Warning: the following files are version controlled and match your ignore pattern: %s These files will continue to be version controlled unless you 'bzr remove' them.

List ignored files and the patterns that matched them.

List all the ignored files and the ignore pattern that caused the file to be ignored.

Alternatively, to list just the files::

not a valid revision-number: %r