-=[ Mr. Bumblebee ]=-
_Indonesia_
jaPc @@ sa d Z d d l m Z d d l Z d d l m Z m Z m Z m Z d Z d Z d Z
d Z d Z d
e j
f d YZ e Z d Z d
Z d Z d Z d e j Z d Z d Z d Z d Z d Z d Z d Z d Z d d d d d d d d d d d d d d d d d d d d g Z dA Z dB Z dC Z! dD Z" dE Z# e j$ dF e dG e j$ dH e dI e
e j$ dJ e dK e
dL Z% dM Z& e j$ dN e% dO e j$ dP e& dQ e j$ dR e dS e j$ dT e dU e j$ dV e dW e j$ dX e dY dZ Z' e j$ d[ e' d\ e j$ d] e d^ e j$ d_ e d` e j( da db dc dd e j( de df dg dh e j$ di e dj e j$ dk e dl e j$ dm e dn e j$ do e dp e j$ dq e dr e j$ ds e dt e j$ du e dv e e j$ dw e dx e e j$ dy e dz e e j$ d{ e d| e e j$ d} e d~ e e j$ d e# d e e j$ d e d e e j$ d e d e e j$ d e d e e j$ d e d e e j$ d e d e e j$ d e! d e e j$ d e" d e d e) f d YZ* d Z+ d e) f d YZ, d Z- d e) f d YZ. d S( s5 A collection of extra help information for using bzr.
Help topics are meant to be help for items that aren't commands, but will
help bzr become fully learnable without referring to a tutorial.
Limited formatting of help text is permitted to make the text useful
both within the reference manual (reStructuredText) and on the screen.
The help text should be reStructuredText with formatting kept to a
minimum and, in particular, no headings. The onscreen renderer applies
the following simple rules before rendering the text:
1. A '::' appearing on the end of a line is replaced with ':'.
2. Lines starting with a ':' have it stripped.
These rules mean that literal blocks and field lists respectively can
be used in the help text, producing sensible input to a manual while
rendering on the screen naturally.
i ( t absolute_importN( t configt osutilst registryt i18nt commandt conceptt hiddent listt plugint HelpTopicRegistryc B@ sJ e Z d Z e d Z e d Z d Z d Z d Z d Z RS( s/ A Registry customized for handling help topics.c C@ s/ | | f } t t | j | | d | d S( s Register a new help topic.
:param topic: Name of documentation entry
:param detail: Function or string object providing detailed
documentation for topic. Function interface is detail(topic).
This should return a text string of the detailed information.
See the module documentation for details on help text formatting.
:param summary: String providing single-line documentation for topic.
:param section: Section in reference manual - see SECT_* identifiers.
t infoN( t superR
t register( t selft topict detailt summaryt sectionR ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR
: s c C@ s2 | | f } t t | j | | | d | d S( s Register a new help topic, and import the details on demand.
:param topic: Name of documentation entry
:param module_name: The module to find the detailed help.
:param member_name: The member of the module to use for detailed help.
:param summary: String providing single-line documentation for topic.
:param section: Section in reference manual - see SECT_* identifiers.
R N( R R
t
register_lazy( R R t module_namet member_nameR R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR I s c C@ s- | j | } t | r% | | S| Sd S( s' Get the detailed help on a given topic.N( t gett callable( R R t obj( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt
get_detailX s
c C@ s+ | j | } | d k r d S| d Sd S( s* Get the single line summary for the topic.i N( t get_infot None( R R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_summary` s c C@ s+ | j | } | d k r d S| d Sd S( s Get the section for the topic.i N( R R ( R R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_sectionh s c C@ sI t } x9 | j D]+ } | | j | k r | j | q q W| S( s# Get the set of topics in a section.( t sett keysR t add( R R t resultR ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_topics_for_sectionp s
(
t __name__t
__module__t __doc__t SECT_LISTR
R R R R R" ( ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR
7 s c C@ so t j } t d | D } g } x7 | D]/ } t j | } | j d | | | f q/ Wd j | S( s( Write out the help for topics to outfilec s@ s | ] } t | Vq d S( N( t len( t .0R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pys <genexpr> s s %-*s %s
t ( t topic_registryR t maxR t appendt join( t dummyt topicst lmaxt outR R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt _help_on_topics~ s
c C@ s) t j d d | f } t j d | S( s[ Load help from a file.
Topics are expected to be txt files in bzrlib.help_topics.
t ens %s.txts bzrlib.help_topics( R t pathjoint resource_string( t
topic_namet
resource_name( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt _load_from_file s c
C@ sB d d l } d d l } g } | j d g } | j d | j d | j d | j } x | j j j D] \ } } | j } | | j j j k r d } | d } nI | j
d d \ } } x. | d
d k s | d d
k r | d } q W| j d | j | f | j d | j | f qs Wd j | | S( s% Generate the help for revision specs.i Ns Revision Identifiers
A revision identifier refers to a specific state of a branch's history. It
can be expressed in several ways. It can begin with a keyword to
unambiguously specify a given lookup type; some examples are 'last:1',
'before:yesterday' and 'submit:'.
Alternately, it can be given without a keyword, in which case it will be
checked as a revision number, a tag, a revision id, a date specification, or a
branch specification, in that order. For example, 'date:today' could be
written as simply 'today', though if you have a tag called 'today' that will
be found first.
If 'REV1' and 'REV2' are revision identifiers, then 'REV1..REV2' denotes a
revision range. Examples: '3647..3649', 'date:yesterday..-1' and
'branch:/path/to/branch1/..branch:/branch2' (note that there are no quotes or
spaces around the '..').
Ranges are interpreted differently by different commands. To the "log" command,
a range is a sequence of log messages, but to the "diff" command, the range
denotes a change between revisions (and not a sequence of changes). In
addition, "log" considers a closed range whereas "diff" and "merge" consider it
to be open-ended, that is, they include one end but not the other. For example:
"bzr log -r 3647..3649" shows the messages of revisions 3647, 3648 and 3649,
while "bzr diff -r 3647..3649" includes the changes done in revisions 3648 and
3649, but not 3647.
The keywords used as revision selection methods are the following:
s1
In addition, plugins can provide other keywords.s8
A detailed description of each keyword is given below.
s ^ s N/As
i is
it s :%s
%ss :%s
%s(
t ret bzrlib.revisionspecR, t compilet MULTILINEt revisionspect revspec_registryt iteritemst help_txtt RevisionSpect splitt prefixR- (
t nameR: t bzrlibR1 t detailst indent_reRD t it docR ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt _help_on_revisionspec s(
# c
@ s d d l m } d d l d f d } d } g } g } | j } | j | xm | D]e } | j | } | s qc n | j d r | j | | | d qc | j | | | d qc Wd d d
j | } t | r | d d
j | 7} n | d 7} | S(
Ni ( t transport_list_registryi c @ sG j | | | d t } d d | } | j | } d | | f S( Nt break_long_wordss
R9 s %-20s%s
( t wrapt FalseR- ( t protot helpt maxlt prefix_widtht
help_linest line_with_indentt help_text( t textwrap( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt
add_string s
c S@ sO | | j d } | | j d } | | k r7 d
S| | k rG d Sd Sd S( Ns ://i ii ( t rfind( t at bt a1t b1( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt sort_func s s ://iO s URL Identifiers
s Supported URL prefixes::
s s
Supported modifiers::
s
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`.
(
t bzrlib.transportRL RW R t sortt get_helpt endswithR, R- R' (
RE RL RX R^ t protlt declt protosRP t shorthelpR1 ( ( RW s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt _help_on_transport s.
s? Bazaar %s -- a free distributed version-control tool
http://bazaar.canonical.com/
Basic commands:
bzr init makes this directory a versioned branch
bzr branch make a copy of another branch
bzr add make files or directories versioned
bzr ignore ignore a file or pattern
bzr mv move or rename a versioned file
bzr status summarize changes in working copy
bzr diff show detailed diffs
bzr merge pull in changes from another branch
bzr commit save some or all changes
bzr send send changes via email
bzr log show history of changes
bzr check validate storage
bzr help init more help on e.g. init command
bzr help commands list all commands
bzr help topics list all help topics
sS Global Options
These options may be used with any command, and may appear in front of any
command. (e.g. ``bzr --profile help``).
--version Print the version number. Must be supplied before the command.
--no-aliases Do not process command aliases when running this command.
--builtin Use the built-in version of a command, not the plugin version.
This does not suppress other plugin effects.
--no-plugins Do not process any plugins.
--no-l10n Do not translate messages.
--concurrency Number of processes that can be run concurrently (selftest).
--profile Profile execution using the hotshot profiler.
--lsprof Profile execution using the lsprof profiler.
--lsprof-file Profile execution using the lsprof profiler, and write the
results to a specified file. If the filename ends with ".txt",
text format will be used. If the filename either starts with
"callgrind.out" or end with ".callgrind", the output will be
formatted for use with KCacheGrind. Otherwise, the output
will be a pickle.
--coverage Generate line coverage report in the specified directory.
-Oname=value Override the ``name`` config option setting it to ``value`` for
the duration of the command. This can be used multiple times if
several options need to be overridden.
See http://doc.bazaar.canonical.com/developers/profiling.html for more
information on profiling.
A number of debug flags are also available to assist troubleshooting and
development. See :doc:`debug-flags-help`.
s Standard Options
Standard options are legal for all commands.
--help, -h Show help message.
--verbose, -v Display more information.
--quiet, -q Only display errors and warnings.
Unlike global options, standard options can be used in aliases.
sT Checkouts
Checkouts are source trees that are connected to a branch, so that when
you commit in the source tree, the commit goes into that branch. They
allow you to use a simpler, more centralized workflow, ignoring some of
Bazaar's decentralized features until you want them. Using checkouts
with shared repositories is very similar to working with SVN or CVS, but
doesn't have the same restrictions. And using checkouts still allows
others working on the project to use whatever workflow they like.
A checkout is created with the bzr checkout command (see "help checkout").
You pass it a reference to another branch, and it will create a local copy
for you that still contains a reference to the branch you created the
checkout from (the master branch). Then if you make any commits they will be
made on the other branch first. This creates an instant mirror of your work, or
facilitates lockstep development, where each developer is working together,
continuously integrating the changes of others.
However the checkout is still a first class branch in Bazaar terms, so that
you have the full history locally. As you have a first class branch you can
also commit locally if you want, for instance due to the temporary loss af a
network connection. Use the --local option to commit to do this. All the local
commits will then be made on the master branch the next time you do a non-local
commit.
If you are using a checkout from a shared branch you will periodically want to
pull in all the changes made by others. This is done using the "update"
command. The changes need to be applied before any non-local commit, but
Bazaar will tell you if there are any changes and suggest that you use this
command when needed.
It is also possible to create a "lightweight" checkout by passing the
--lightweight flag to checkout. A lightweight checkout is even closer to an
SVN checkout in that it is not a first class branch, it mainly consists of the
working tree. This means that any history operations must query the master
branch, which could be slow if a network connection is involved. Also, as you
don't have a local branch, then you cannot commit locally.
Lightweight checkouts work best when you have fast reliable access to the
master branch. This means that if the master branch is on the same disk or LAN
a lightweight checkout will be faster than a heavyweight one for any commands
that modify the revision history (as only one copy of the branch needs to
be updated). Heavyweight checkouts will generally be faster for any command
that uses the history but does not change it, but if the master branch is on
the same disk then there won't be a noticeable difference.
Another possible use for a checkout is to use it with a treeless repository
containing your branches, where you maintain only one working tree by
switching the master branch that the checkout points to when you want to
work on a different branch.
Obviously to commit on a checkout you need to be able to write to the master
branch. This means that the master branch must be accessible over a writeable
protocol , such as sftp://, and that you have write permissions at the other
end. Checkouts also work on the local file system, so that all that matters is
file permissions.
You can change the master of a checkout by using the "switch" command (see
"help switch"). This will change the location that the commits are sent to.
The "bind" command can also be used to turn a normal branch into a heavy
checkout. If you would like to convert your heavy checkout into a normal
branch so that every commit is local, you can use the "unbind" command. To see
whether or not a branch is bound or not you can use the "info" command. If the
branch is bound it will tell you the location of the bound branch.
Related commands::
checkout Create a checkout. Pass --lightweight to get a lightweight
checkout
update Pull any changes in the master branch in to your checkout
commit Make a commit that is sent to the master branch. If you have
a heavy checkout then the --local option will commit to the
checkout without sending the commit to the master
switch Change the master branch that the commits in the checkout will
be sent to
bind Turn a standalone branch into a heavy checkout so that any
commits will be sent to the master branch
unbind Turn a heavy checkout into a standalone branch so that any
commits are only made locally
info Displays whether a branch is bound or unbound. If the branch is
bound, then it will also display the location of the bound branch
s Repositories
Repositories in Bazaar are where committed information is stored. There is
a repository associated with every branch.
Repositories are a form of database. Bzr will usually maintain this for
good performance automatically, but in some situations (e.g. when doing
very many commits in a short time period) you may want to ask bzr to
optimise the database indices. This can be done by the 'bzr pack' command.
By default just running 'bzr init' will create a repository within the new
branch but it is possible to create a shared repository which allows multiple
branches to share their information in the same location. When a new branch is
created it will first look to see if there is a containing shared repository it
can use.
When two branches of the same project share a repository, there is
generally a large space saving. For some operations (e.g. branching
within the repository) this translates in to a large time saving.
To create a shared repository use the init-repository command (or the alias
init-repo). This command takes the location of the repository to create. This
means that 'bzr init-repository repo' will create a directory named 'repo',
which contains a shared repository. Any new branches that are created in this
directory will then use it for storage.
It is a good idea to create a repository whenever you might create more
than one branch of a project. This is true for both working areas where you
are doing the development, and any server areas that you use for hosting
projects. In the latter case, it is common to want branches without working
trees. Since the files in the branch will not be edited directly there is no
need to use up disk space for a working tree. To create a repository in which
the branches will not have working trees pass the '--no-trees' option to
'init-repository'.
Related commands::
init-repository Create a shared repository. Use --no-trees to create one
in which new branches won't get a working tree.
s Working Trees
A working tree is the contents of a branch placed on disk so that you can
see the files and edit them. The working tree is where you make changes to a
branch, and when you commit the current state of the working tree is the
snapshot that is recorded in the commit.
When you push a branch to a remote system, a working tree will not be
created. If one is already present the files will not be updated. The
branch information will be updated and the working tree will be marked
as out-of-date. Updating a working tree remotely is difficult, as there
may be uncommitted changes or the update may cause content conflicts that are
difficult to deal with remotely.
If you have a branch with no working tree you can use the 'checkout' command
to create a working tree. If you run 'bzr checkout .' from the branch it will
create the working tree. If the branch is updated remotely, you can update the
working tree by running 'bzr update' in that directory.
If you have a branch with a working tree that you do not want the 'remove-tree'
command will remove the tree if it is safe. This can be done to avoid the
warning about the remote working tree not being updated when pushing to the
branch. It can also be useful when working with a '--no-trees' repository
(see 'bzr help repositories').
If you want to have a working tree on a remote machine that you push to you
can either run 'bzr update' in the remote branch after each push, or use some
other method to update the tree during the push. There is an 'rspush' plugin
that will update the working tree using rsync as well as doing a push. There
is also a 'push-and-update' plugin that automates running 'bzr update' via SSH
after each push.
Useful commands::
checkout Create a working tree when a branch does not have one.
remove-tree Removes the working tree from a branch when it is safe to do so.
update When a working tree is out of sync with its associated branch
this will update the tree to match the branch.
sk Branches
A branch consists of the state of a project, including all of its
history. All branches have a repository associated (which is where the
branch history is stored), but multiple branches may share the same
repository (a shared repository). Branches can be copied and merged.
In addition, one branch may be bound to another one. Binding to another
branch indicates that commits which happen in this branch must also
happen in the other branch. Bazaar ensures consistency by not allowing
commits when the two branches are out of date. In order for a commit
to succeed, it may be necessary to update the current branch using
``bzr update``.
Related commands::
init Change a directory into a versioned branch.
branch Create a new branch that is a copy of an existing branch.
merge Perform a three-way merge.
bind Bind a branch to another one.
sW Standalone Trees
A standalone tree is a working tree with an associated repository. It
is an independently usable branch, with no dependencies on any other.
Creating a standalone tree (via bzr init) is the quickest way to put
an existing project under version control.
Related Commands::
init Make a directory into a versioned branch.
s- Status Flags
Status flags are used to summarise changes to the working tree in a concise
manner. They are in the form::
xxx <filename>
where the columns' meanings are as follows.
Column 1 - versioning/renames::
+ File versioned
- File unversioned
R File renamed
? File unknown
X File nonexistent (and unknown to bzr)
C File has conflicts
P Entry for a pending merge (not a file)
Column 2 - contents::
N File created
D File deleted
K File kind changed
M File modified
Column 3 - execute::
* The execute bit was changed
t BZRPATHs= Path where bzr is to look for shell plugin external commands.t BZR_EMAILs, E-Mail address of the user. Overrides EMAIL.t EMAILs E-Mail address of the user.t
BZR_EDITORs5 Editor for editing commit messages. Overrides EDITOR.t EDITORs# Editor for editing commit messages.t BZR_PLUGIN_PATHs( Paths where bzr should look for plugins.t BZR_DISABLE_PLUGINSs! Plugins that bzr should not load.t BZR_PLUGINS_ATs8 Plugins to load from a directory not in BZR_PLUGIN_PATH.t BZR_HOMEs5 Directory holding .bazaar config dir. Overrides HOME.s BZR_HOME (Win32)s@ Directory holding bazaar config dir. Overrides APPDATA and HOME.t BZR_REMOTE_PATHs8 Full name of remote 'bzr' command (for bzr+ssh:// URLs).t BZR_SSHsG Path to SSH client, or one of paramiko, openssh, sshcorp, plink or lsh.t BZR_LOGs7 Location of .bzr.log (use '/dev/null' to suppress log).s BZR_LOG (Win32)s1 Location of .bzr.log (use 'NUL' to suppress log).t BZR_COLUMNSs! Override implicit terminal width.t BZR_CONCURRENCYs; Number of processes that can be run concurrently (selftest)t BZR_PROGRESS_BARs; Override the progress display. Values are 'none' or 'text'.t BZR_PDBs. Control whether to launch a debugger on error.t BZR_SIGQUIT_PDBsG Control whether SIGQUIT behaves normally or invokes a breakin debugger.t BZR_TEXTUI_INPUTsK Force console input mode for prompts to line-based (instead of char-based).c C@ s d d l } d g } t g t D] } t | d ^ q } d | d } | j d | d d | d xw t D]o \ } } | j | | d t | d | j d j | j | d | d
d | d | j d qt W| d | d d | d 7} d j | S( Ni sE Environment Variables
See bzr help configuration for more details.
iP i t =R9 s
i t widtht subsequent_indentR) ( RW R+ t known_env_variablesR' R, R- RN ( R RW t rett kt max_key_lent desc_lent desc( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt _env_variablesm s )!#! s Files
:On Unix: ~/.bazaar/bazaar.conf
:On Windows: C:\\Documents and Settings\\username\\Application Data\\bazaar\\2.0\\bazaar.conf
Contains the user's default configuration. The section ``[DEFAULT]`` is
used to define general configuration that will be applied everywhere.
The section ``[ALIASES]`` can be used to create command aliases for
commonly used options.
A typical config file might look something like::
[DEFAULT]
email=John Doe <jdoe@isp.com>
[ALIASES]
commit = commit --strict
log10 = log --short -r -10..-1
se Criss-Cross
A criss-cross in the branch history can cause the default merge technique
to emit more conflicts than would normally be expected.
In complex merge cases, ``bzr merge --lca`` or ``bzr merge --weave`` may give
better results. You may wish to ``bzr revert`` the working tree and merge
again. Alternatively, use ``bzr remerge`` on particular conflicted files.
Criss-crosses occur in a branch's history if two branches merge the same thing
and then merge one another, or if two branches merge one another at the same
time. They can be avoided by having each branch only merge from or into a
designated central branch (a "star topology").
Criss-crosses cause problems because of the way merge works. Bazaar's default
merge is a three-way merger; in order to merge OTHER into THIS, it must
find a basis for comparison, BASE. Using BASE, it can determine whether
differences between THIS and OTHER are due to one side adding lines, or
from another side removing lines.
Criss-crosses mean there is no good choice for a base. Selecting the recent
merge points could cause one side's changes to be silently discarded.
Selecting older merge points (which Bazaar does) mean that extra conflicts
are emitted.
The ``weave`` merge type is not affected by this problem because it uses
line-origin detection instead of a basis revision to determine the cause of
differences.
s Branches Out of Sync
When reconfiguring a checkout, tree or branch into a lightweight checkout,
a local branch must be destroyed. (For checkouts, this is the local branch
that serves primarily as a cache.) If the branch-to-be-destroyed does not
have the same last revision as the new reference branch for the lightweight
checkout, data could be lost, so Bazaar refuses.
How you deal with this depends on *why* the branches are out of sync.
If you have a checkout and have done local commits, you can get back in sync
by running "bzr update" (and possibly "bzr commit").
If you have a branch and the remote branch is out-of-date, you can push
the local changes using "bzr push". If the local branch is out of date, you
can do "bzr pull". If both branches have had changes, you can merge, commit
and then push your changes. If you decide that some of the changes aren't
useful, you can "push --overwrite" or "pull --overwrite" instead.
ss Storage Formats
To ensure that older clients do not access data incorrectly,
Bazaar's policy is to introduce a new storage format whenever
new features requiring new metadata are added. New storage
formats may also be introduced to improve performance and
scalability.
The newest format, 2a, is highly recommended. If your
project is not using 2a, then you should suggest to the
project owner to upgrade.
.. note::
Some of the older formats have two variants:
a plain one and a rich-root one. The latter include an additional
field about the root of the tree. There is no performance cost
for using a rich-root format but you cannot easily merge changes
from a rich-root format into a plain format. As a consequence,
moving a project to a rich-root format takes some co-ordination
in that all contributors need to upgrade their repositories
around the same time. 2a and all future formats will be
implicitly rich-root.
See :doc:`current-formats-help` for the complete list of
currently supported formats. See :doc:`other-formats-help` for
descriptions of any available experimental and deprecated formats.
R> s Explain how to use --revisiont basics Basic commandsR/ s Topics listc C@ s$ d d l m } d | j j | S( Ni ( t
controldirs Current Storage Formats
( RF R t format_registryt
help_topic( R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_current_formats_topic s c C@ s$ d d l m } d | j j | S( Ni ( R s Other Storage Formats
( RF R R R ( R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_other_formats_topic s s current-formatss Current storage formatss
other-formatss+ Experimental and deprecated storage formatss standard-optionss) Options that can be used with any commands global-optionss$ Options that control how Bazaar runst urlspecs Supported transport protocolss status-flagss Help on status flagsc C@ s$ d d l m } d | j j | S( Ni ( t
bugtrackers Bug Tracker Settings
( RF R t tracker_registryR ( R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_bugs_topic s t bugss Bug tracker settingss
env-variabless% Environment variable names and valuest filess* Information on configuration and log filest hookss bzrlib.hookst hooks_help_texts. Points at which custom processing can be addeds location-aliass bzrlib.directory_services AliasDirectory.help_texts Aliases for remembered locationst authentications) Information on configuring authenticationt
configurations/ Details on the configuration settings availables conflict-typess, Types of conflicts and what to do about thems debug-flagss+ Options to show or record debug informations log-formatss( Details on the logging formats availables url-special-charss" Special character handling in URLst branchess Information on what a branch ist checkoutss! Information on what a checkout iss content-filterss- Conversion of content into/from working treess diverged-branchess How to fix diverged branchest eols# Information on end-of-line handlingt formatss( Information on choosing a storage formatt patternss! Information on the pattern syntaxt repositoriess) Basic information on shared repositories.t ruless. Information on defining rule-based preferencess standalone-treess( Information on what a standalone tree iss
working-treess Information on working treess criss-crosss" Information on criss-cross mergings sync-for-reconfigures1 Steps to resolve "out-of-sync" when reconfiguringt HelpTopicIndexc B@ s e Z d Z d Z d Z RS( s) A index for bzr help that returns topics.c C@ s
d | _ d S( NR) ( RD ( R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt __init__J s c C@ s6 | d k r d } n | t k r. t | g Sg Sd S( s Search for topic in the HelpTopicRegistry.
:param topic: A topic to search for. None is treated as 'basic'.
:return: A list which is either empty or contains a single
RegisteredTopic entry.
R N( R R* t RegisteredTopic( R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt
get_topicsM s
( R# R$ R% R R ( ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR G s c C@ sF d } | rB | d 7} | d j t t | 7} | d 7} n | S( NR) s
:See also: s , s
( R- t sortedR ( t see_alsoR! ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt _format_see_also\ s
R c B@ s/ e Z d Z d Z d e d Z d Z RS( s A help topic which has been registered in the HelpTopicRegistry.
These topics consist of nothing more than the name of the topic - all
data is retrieved on demand from the registry.
c C@ s
| | _ d S( sX Constructor.
:param topic: The name of the topic that this represents.
N( R ( R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR l s c C@ sT t j | j } | t | 7} | r7 t | } n t j t j | } | S( s Return a string with the help for this topic.
:param additional_see_also: Additional help topics to be
cross-referenced.
:param plain: if False, raw help (reStructuredText) is
returned instead of plain text.
( R* R R R t help_as_plain_textR t installt gettext_per_paragraph( R t additional_see_alsot plainR! ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt
get_help_texts s
c C@ s | j S( s. Return the help topic this can be found under.( R ( R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt get_help_topic s N( R# R$ R% R R t TrueR R ( ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR e s c C@ s d d l } | j d d | } | j } g } xh | D]` } | j d r\ | d } n | j d rx | d } n | j d d
| } | j | q: Wd j | d S( s4 Minimal converter of reStructuredText to plain text.i Ns (?m)^\s*::\n\s*$R) t :i s ::is :doc:`(.+?)-help`s ``bzr help \1``s
( R: t subt
splitlinest
startswithRb R, R- ( t textR: t linesR! t line( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR s
t ConfigOptionHelpIndexc B@ s e Z d Z d Z d Z RS( s9 A help index that returns help topics for config options.c C@ s
d | _ d S( Ns configuration/( RD ( R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR s c C@ sb | d k r g S| j | j r8 | t | j } n | t j k rZ t j j | g Sg Sd S( s Search for topic in the registered config options.
:param topic: A topic to search for.
:return: A list which is either empty or contains a single
config.Option entry.
N( R R RD R' R t option_registryR ( R R ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR s ( R# R$ R% R R ( ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyR s ( Rh s= Path where bzr is to look for shell plugin external commands.( Ri s, E-Mail address of the user. Overrides EMAIL.( Rj s E-Mail address of the user.( Rk s5 Editor for editing commit messages. Overrides EDITOR.( Rl s# Editor for editing commit messages.( Rm s( Paths where bzr should look for plugins.( Rn s! Plugins that bzr should not load.( Ro s8 Plugins to load from a directory not in BZR_PLUGIN_PATH.( Rp s5 Directory holding .bazaar config dir. Overrides HOME.( s BZR_HOME (Win32)s@ Directory holding bazaar config dir. Overrides APPDATA and HOME.( Rq s8 Full name of remote 'bzr' command (for bzr+ssh:// URLs).( Rr sG Path to SSH client, or one of paramiko, openssh, sshcorp, plink or lsh.( Rs s7 Location of .bzr.log (use '/dev/null' to suppress log).( s BZR_LOG (Win32)s1 Location of .bzr.log (use 'NUL' to suppress log).( Rt s! Override implicit terminal width.( Ru s; Number of processes that can be run concurrently (selftest)( Rv s; Override the progress display. Values are 'none' or 'text'.( Rw s. Control whether to launch a debugger on error.( Rx sG Control whether SIGQUIT behaves normally or invokes a breakin debugger.( Ry sK Force console input mode for prompts to line-based (instead of char-based).(/ R% t
__future__R RF R R R R t SECT_COMMANDt SECT_CONCEPTt SECT_HIDDENR& t SECT_PLUGINt RegistryR
R* R2 R8 RK Rg t __version__t _basic_helpt _global_optionst _standard_optionst
_checkoutst
_repositoriest _working_treest _branchest _standalone_treest
_status_flagsR} R t _filest _criss_crosst _branches_out_of_synct _storage_formatsR
R R R R t objectR R R R R ( ( ( s? /usr/lib/python2.7/dist-packages/bzrlib/help_topics/__init__.pyt <module>" s " B
? `
$ U**! "
#
Copyright © 2017 || Recoded By Mr.Bumblebee