Translations by Gianfranco Frisani

:mainline:

Select the revision that merged the specified revision into mainline.

:last:

Supply a positive number to get the nth revision from the end. This is the same as supplying negative numbers to the 'revno:' spec. Examples::

last:1 -> return the last revision last:3 -> return the revision 2 before the end.

Rules =====

Rules are defined in ini file format where the sections are file glob patterns and the contents of each section are the preferences for files matching that pattern(s). For example::

[name *.bat] eol = native

[name *.html *.xml] keywords = xml_escape

Preferences like these are useful for commands and plugins wishing to provide custom behaviour for selected files. For more information on end of line conversion see :doc:`eol-help`. Keyword support is provided by the `keywords plugin <http://doc.bazaar.canonical.com/plugins/en/keywords-plugin.html>`_.

Files -----

Default rules for all branches are defined in the optional file ``BZR_HOME/rules``.

Rule Patterns -------------

Patterns are ordered and searching stops as soon as one matches. As a consequence, more explicit patterns should be placed towards the top of the file. Rule patterns use exactly the same conventions as ignore patterns. See :doc:`patterns-help` for details.

.. note::

Patterns containing square brackets or spaces should be surrounded in quotes to ensure they are correctly parsed.

authentication Information on configuring authentication basic Basic commands branches Information on what a branch is bugs Bug tracker settings checkouts Information on what a checkout is commands Basic help for all commands configuration Details on the configuration settings available conflict-types Types of conflicts and what to do about them content-filters Conversion of content into/from working trees criss-cross Information on criss-cross merging current-formats Current storage formats debug-flags Options to show or record debug information diverged-branches How to fix diverged branches env-variables Environment variable names and values eol Information on end-of-line handling files Information on configuration and log files formats Information on choosing a storage format global-options Options that control how Bazaar runs hidden-commands All hidden commands hooks Points at which custom processing can be added launchpad Using Bazaar with Launchpad.net location-alias Aliases for remembered locations log-formats Details on the logging formats available other-formats Experimental and deprecated storage formats patterns Information on the pattern syntax repositories Basic information on shared repositories. revisionspec Explain how to use --revision rules Information on defining rule-based preferences standalone-trees Information on what a standalone tree is standard-options Options that can be used with any command status-flags Help on status flags sync-for-reconfigure Steps to resolve "out-of-sync" when reconfiguring topics Topics list url-special-chars Special character handling in URLs urlspec Supported transport protocols working-trees Information on working trees

Special character handling in URLs ==================================

Bazaar allows locations to be specified in multiple ways, either:

* Fully qualified URLs

* File system paths, relative or absolute

Internally bzr treats all locations as URLs. For any file system paths that are specified it will automatically determine the appropriate URL representation, and escape special characters where necessary.

There are a few characters which have special meaning in URLs and need careful handling to avoid ambiguities. Characters can be escaped with a % and a hex value in URLs. Any non-ASCII characters in a file path will automatically be urlencoded when the path is converted to a URL.

URLs represent non-ASCII characters in an encoding defined by the server, but usually UTF-8. The % escapes should be of the UTF-8 bytes. Bazaar tries to be generous in what it accepts as a URL and to print them in a way that will be readable.

For example, if you have a directory named '/tmp/%2False' these are all valid ways of accessing the content (0x2F, or 47, is the ASCII code for forward slash)::

cd /tmp bzr log /tmp/%2False bzr log %2False bzr log file:///tmp/%252False bzr log file://localhost/tmp/%252False bzr log file:%252False

These are valid but do not refer to the same file::

bzr log file:///tmp/%2False (refers to a file called /tmp/\/alse) bzr log %252False (refers to a file called /tmp/%252False)

Comma also has special meaning in URLs, because it denotes `segment parameters`_

_`segment parameters`: http://www.ietf.org/rfc/rfc3986.txt (section 3.3)

Comma is also special in any file system paths that are specified. To use a literal comma in a file system path, specify a URL and URL encode the comma::

bzr log foo,branch=bla # path "foo" with the segment parameter "branch" set to "bla" bzr log file:foo%2Cbranch=bla # path "foo,branch=bla" bzr log file:foo,branch=bla # path "foo" with segment parameter "branch" set to "bla"

URL Identifiers

Supported URL prefixes::

aftp:// Access using active FTP. bzr:// Fast access using the Bazaar smart server. bzr+ssh:// Fast access using the Bazaar smart server over SSH. file:// Access using the standard filesystem (default) ftp:// Access using passive FTP. http:// Read-only access of branches exported on the web. https:// Read-only access of branches exported on the web using SSL. sftp:// Access using SFTP (most SSH servers provide SFTP).

Supported modifiers::

gio+ Access using any GIO supported protocols.

Bazaar supports all of the standard parts within the URL::

<protocol>://[user[:password]@]host[:port]/[path]

allowing URLs such as::

http://bzruser:BadPass@bzr.example.com:8080/bzr/trunk

For bzr+ssh:// and sftp:// URLs, Bazaar also supports paths that begin with '~' as meaning that the rest of the path should be interpreted relative to the remote user's home directory. For example if the user ``remote`` has a home directory of ``/home/remote`` on the server shell.example.com, then::

bzr+ssh://remote@shell.example.com/~/myproject/trunk

would refer to ``/home/remote/myproject/trunk``.

Many commands that accept URLs also accept location aliases too. See :doc:`location-alias-help` and :doc:`url-special-chars-help`.