-=[ Mr. Bumblebee ]=-
_Indonesia_

Path : /usr/lib/python2.7/dist-packages/bzrlib/
Current File : //usr/lib/python2.7/dist-packages/bzrlib/builtins.pyc
ó
;ÝZc@@s$	dZddlmZddlZddlZddlmZejeƒdƒddlm	Z	m
Z
mZddlm
Z
mZmZmZmZddlmZmZmZmZmZdd	lmZed
„Zed„Zed„Zed
„Zeeed„Zed„Zd„Z d„Z!eed„Z"d„Z#d„Z$de	fd„ƒYZ%de	fd„ƒYZ&de	fd„ƒYZ'de	fd„ƒYZ(de	fd„ƒYZ)de	fd „ƒYZ*d!e	fd"„ƒYZ+d#e	fd$„ƒYZ,d%e	fd&„ƒYZ-d'e	fd(„ƒYZ.d)e	fd*„ƒYZ/d+e	fd,„ƒYZ0d-e	fd.„ƒYZ1d/e	fd0„ƒYZ2d1e	fd2„ƒYZ3d3e	fd4„ƒYZ4d5e	fd6„ƒYZ5d7e	fd8„ƒYZ6d9e	fd:„ƒYZ7d;e	fd<„ƒYZ8d=e	fd>„ƒYZ9d?e	fd@„ƒYZ:dAe	fdB„ƒYZ;dCe	fdD„ƒYZ<dEe	fdF„ƒYZ=dGe	fdH„ƒYZ>dIe	fdJ„ƒYZ?dKe	fdL„ƒYZ@dMe	fdN„ƒYZAdOe	fdP„ƒYZBdQe	fdR„ƒYZCdSe	fdT„ƒYZDdUe	fdV„ƒYZEdW„ZFdX„ZGdYe	fdZ„ƒYZHd[„ZId\„ZJeKeKeKd]d^„ZLd_e	fd`„ƒYZMdae	fdb„ƒYZNdce	fdd„ƒYZOdee	fdf„ƒYZPdge	fdh„ƒYZQdie	fdj„ƒYZRdke	fdl„ƒYZSdme	fdn„ƒYZTdoe	fdp„ƒYZUdqe	fdr„ƒYZVdse	fdt„ƒYZWdue	fdv„ƒYZXdwe	fdx„ƒYZYdye	fdz„ƒYZZd{e	fd|„ƒYZ[d}e	fd~„ƒYZ\de	fd€„ƒYZ]de	fd‚„ƒYZ^dƒe	fd„„ƒYZ_d…e	fd†„ƒYZ`d‡e	fdˆ„ƒYZad‰e	fdŠ„ƒYZbd‹e	fdŒ„ƒYZcde	fdŽ„ƒYZdde	fd„ƒYZed‘e	fd’„ƒYZfd“e	fd”„ƒYZgd•e	fd–„ƒYZhd—e	fd˜„ƒYZid™e	fdš„ƒYZjd›e	fdœ„ƒYZkde	fdž„ƒYZldŸe	fd „ƒYZmd¡e	fd¢„ƒYZnd£e	fd¤„ƒYZod¥e	fd¦„ƒYZpd§e	fd¨„ƒYZqd©e	fdª„ƒYZrd«e	fd¬„ƒYZsde	fd®„ƒYZtd¯e	fd°„ƒYZud±eufd²„ƒYZvd³e	fd´„ƒYZwdµe	fd¶„ƒYZxd·e	fd¸„ƒYZyd¹e	fdº„ƒYZzd»e	fd¼„ƒYZ{d½e	fd¾„ƒYZ|d¿e	fdÀ„ƒYZ}dÁe	fdÂ„ƒYZ~dÃe	fdÄ„ƒYZdÅe	fdÆ„ƒYZ€dÇe	fdÈ„ƒYZdÉe	fdÊ„ƒYZ‚dË„ZƒdS(Ìsbuiltin bzr commandsi(tabsolute_importN(tlazy_imports
import cStringIO
import errno
import sys
import time

import bzrlib
from bzrlib import (
    bugtracker,
    bundle,
    btree_index,
    controldir,
    directory_service,
    delta,
    config as _mod_config,
    errors,
    globbing,
    hooks,
    log,
    merge as _mod_merge,
    merge_directive,
    osutils,
    reconfigure,
    rename_map,
    revision as _mod_revision,
    static_tuple,
    timestamp,
    transport,
    ui,
    urlutils,
    views,
    gpg,
    )
from bzrlib.branch import Branch
from bzrlib.conflicts import ConflictList
from bzrlib.transport import memory
from bzrlib.revisionspec import RevisionSpec, RevisionInfo
from bzrlib.smtp_connection import SMTPConnection
from bzrlib.workingtree import WorkingTree
from bzrlib.i18n import gettext, ngettext
(tCommandtbuiltin_command_registrytdisplay_command(t
ListOptiontOptiontRegistryOptiontcustom_helpt_parse_revision_str(tmuttertnotetwarningtis_quiettget_verbosity_level(tsymbol_versioningcC@ssy|jƒ}Wntjk
r-|jjSX|dk	r>|S|jd|ƒ}|jƒ}|dk	rl|S|jS(s/Return location of branch for this control dir.tpossible_transportsN(tget_branch_referenceterrorstNotBranchErrortroot_transporttbasetNonetopen_branchtget_bound_location(tcontrol_dirRttargettthis_branchtmaster_location((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_get_branch_locationVs		cC@s©t|d|ƒ}ytjj|d|ƒ}Wntjk
rKt|fSXy|jƒ}Wn$tjtj	fk
r‚t|fSX|j
jož|j|jk|fSdS(sÙCheck if the branch in control_dir is colocated.

    :param control_dir: Control directory
    :return: Tuple with boolean indicating whether the branch is colocated
        and the full URL to the actual branch
    RN(
Rt
controldirt
ControlDirtopenRRtFalsetopen_workingtreet
NoWorkingTreetNotLocalUrlt_formattcolocated_branchestcontrol_url(RRtthis_urltroottwt((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt
_is_colocatedhs		
cC@sˆtjj|ƒ}d|kr„d|kr„t||ƒ\}}|retj|itj|ƒd6ƒStj|dtj|ƒƒSn|S(sÔLookup the location for a new sibling branch.

    :param control_dir: Control directory to find sibling branches from
    :param location: Name of the new branch
    :return: Full location to the new branch
    t/s\tbranchs..(tdirectory_servicetdirectoriestdereferenceR+turlutilstjoin_segment_parameterstescapetjoin(RtlocationRt	colocatedR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytlookup_new_sibling_branch„s	cC@siy|j|d|ƒSWnKtjtjfk
rdt|ƒ}tjtj|dtj	|ƒƒƒSXdS(sÔOpen a branch, possibly a sibling of another.

    :param control_dir: Control directory relative to which to lookup the
        location.
    :param location: Location to look up
    :return: branch to open
    Rs..N(
RRRtNoColocatedBranchSupportRtBranchR R1R4R3(RR5RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytopen_sibling_branch—scC@sƒ|dkrX|dkr!d}nytj|d|ƒSWqXtjk
rTd}qXXntjj|d|ƒ}t||d|ƒS(s®Open a nearby branch.

    :param near: Optional location of container from which to open branch
    :param location: Location of the branch
    :return: Branch instance
    t.RN(RR9R RRRRR:(tnearR5Rtcdir((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytopen_nearby_branchªs	
	cc@sCtƒ}y|jƒ}WnCtjk
r^x+|jƒjƒD]\}}||fVq?WdSX|dk	rƒtj|d|ƒ}nd}|dksž|j	rç|dk	r¶|j
}nx†|jƒjƒD]\}}||fVqÉWnX|j
jƒ}xF|jdt
ƒD]2}tj|j|jƒjdƒ}||fVq	WdS(s½Iterate over the siblings of a branch.

    :param control_dir: Control directory for which to look up the siblings
    :return: Iterator over tuples with branch name and branch object
    NRtusingR,(tsetRRRtget_branchest	iteritemsRR9R tnametbzrdirtfind_repositoryt
find_branchestTrueR1trelative_urltuser_urltrstrip(RRt	seen_urlst	referenceRCR-t
ref_branchtrepo((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytiter_sibling_branches¿s*	cC@s|r›tj|dƒ\}}|jƒr~|jjƒ}|r~x8|D]-}tj||ƒsGtj||ƒ‚qGqGWq~n|}|j	|ƒ|d<nctjdƒd}|jƒrþ|jjƒ}|rþ|}tj
|ƒ}ttdƒ|ƒqþn||fS(s#
    Return a tree and list of absolute paths from a file list.

    Similar to tree_files, but add handles files a bit differently, so it a
    custom implementation.  In particular, MutableTreeTree.smart_add expects
    absolute paths, which it immediately converts to relative paths.
    iu.s'Ignoring files outside view. View is %s(
tWorkingTreetopen_containingtsupports_viewstviewstlookup_viewtosutilst
is_inside_anyRtFileOutsideViewtabspathtview_display_strRtgettext(t	file_listttreetrelpatht
view_filestfilenametview_str((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyttree_files_for_addßs$
cC@sI|dkrdSt|ƒdkrAtjtdƒ|fƒ‚n|dS(Nis7bzr %s --revision takes exactly one revision identifieri(RtlenRtBzrCommandErrorRZ(tcommand_namet	revisions((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_get_one_revisionÿs	cC@sp|dkr|j}n|dkrN|dk	r?|jƒ}ql|jƒ}nt||ƒ}|j|ƒ}|S(sxGet a revision tree. Not suitable for commands that change the tree.
    
    Specifically, the basis tree in dirstate trees is coupled to the dirstate
    and doing a commit/uncommit/pull will at best fail due to changing the
    basis revision data.

    If tree is passed in, it should be already locked, for lifetime management
    of the trees internal cached state.
    N(RR-t
basis_treeRftas_tree(RdReR-R\trev_treetrevision((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_get_one_revision_tree	s
cC@s\d}y;|jjƒd}|dk	r@||jjƒf}nWntjk
rWnX|S(s:Get the view information from a tree for change reporting.iN(RRSt
get_view_infoRTRtViewsNotSupported(R\t	view_infotcurrent_view((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt"_get_view_info_for_change_reporter scC@s2|dk	r"dtj|ƒ|fStjj|ƒS(sOpen the tree or branch containing the specified file, unless
    the --directory option is used to specify a different branch.N(RR9R RRtopen_containing_tree_or_branch(R_t	directory((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt,_open_directory_or_containing_tree_or_branch,st
cmd_statuscB@s¹eZdZdgZddddedddd	d
ƒedddd	d
ƒedddƒedddƒgZddgZdZdddgZe	e
dde
e
e
e
e
d„ƒZRS(s9Display status summary.

    This reports on versioned and unknown files, reporting them
    grouped by state.  Possible states are:

    added
        Versioned in the working copy but not in 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.

    modified
        Text has changed since the previous revision.

    kind changed
        File kind has been changed (e.g. from file to directory).

    unknown
        Not versioned and not matching an ignore pattern.

    Additionally for directories, symlinks and files with a changed
    executable bit, Bazaar indicates their type using a trailing
    character: '/', '@' or '*' respectively. These decorations can be
    disabled using the '--no-classify' option.

    To see ignored files use 'bzr ignored'.  For details on the
    changes to file texts, use 'bzr diff'.

    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 bzr status -SV.

    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.

    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.

    To compare the working directory to a specific revision, pass a
    single revision to the revision argument.

    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 'bzr diff --summarize'.
    sfile*sshow-idsRjtchangetverbosetshortthelpsUse short status indicators.t
short_nametSt	versionedsOnly show versioned files.tVs
no-pendingsDon't show pending merges.sno-classifys(Do not mark object type using indicator.tsttstattreplacetdifftrevertsstatus-flagsc	C@sãddlm}	|r@t|ƒdkr@tjtdƒƒ‚ntj|ƒ\}
}|dgkr…d}|dgkršt	}qšn|dk	ršt	}n|	|
d|d|d	|d
|j
d|d|d
|d|d|ƒ	dS(Ni(tshow_tree_statusisBbzr status --revision takes exactly one or two revision specifierstR;tshow_idstspecific_filesRjtto_fileRwR{tshow_pendingRvtclassify(t
bzrlib.statusR‚RbRRcRZRPtopen_containing_pathsRRGtoutf(tselfR„R[RjRwR{t
no_pendingRvtno_classifyR‚R\trelfile_list((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytrun†s	
N(
t__name__t
__module__t__doc__t
takes_argsRt
takes_optionstaliasest
encoding_typet	_see_alsoRR!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRt:s"7			tcmd_cat_revisioncB@sPeZdZeZdgZddgZdZd„Ze	dddd„ƒZRS(	sœWrite out metadata for a revision.

    The revision to print can either be specified by a specific
    revision identifier, or you can use --revision.
    srevision_id?RrRjtstrictcC@sw|j|fgdtƒ}|jƒ}|jdkrKtj||ƒ‚n|jdƒ}|jj|j	dƒƒdS(Nt	unorderedtabsenttfulltextsutf-8(
tget_record_streamRGtnexttstorage_kindRtNoSuchRevisiontget_bytes_asR‹twritetdecode(RŒRetrevidtstreamtrecordtrevtext((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytprint_revision®su.c	C@s«|dk	r0|dk	r0tjtdƒƒ‚n|dkr`|dkr`tjtdƒƒ‚ntjj|ƒd}|jj}|dkr¦tjtdƒƒ‚n|jj	ƒzã|dk	r2t
j|dtƒ}y|j
||ƒWq•tjk
r.tdƒj|jj|ƒ}tj|ƒ‚q•Xnc|dk	r•xT|D]I}|dkrotjtdƒƒ‚n|j|ƒ}|j
||ƒqEWnWd|jjƒXdS(Ns4You can only supply one of revision_id or --revisions2You must supply either --revision or a revision_idis;Repository %r does not support access to raw revision textstwarns,The repository {0} contains no revision {1}.s#You cannot specify a NULL revision.(RRRcRZRRRqt
repositoryRet	lock_readRUtsafe_revision_idR!R©R¡tformatRtas_revision_idtunlock(	RŒtrevision_idRjRrtbRetmsgtrevtrev_id((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¶s4

N(R‘R’R“RGthiddenR”R•tencodingR©RRR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR™¡s		tcmd_dump_btreecB@s_eZdZeZdZdgZedddƒgZe	d„Z
d„Zd„Zd	„Z
RS(
s†Dump the contents of a btree index file to stdout.

    PATH is a btree index file, it can be any URL. This includes things like
    .bzr/repository/pack-names, or .bzr/repository/indices/a34b3a...ca4a4.iix

    By default, the tuples stored in the index file will be displayed. With
    --raw, we will uncompress the pages, but otherwise display the raw bytes
    stored in the index.
    texacttpathtrawRxs@Write the uncompressed bytes out, rather than the parsed tuples.cC@sQtj|ƒ\}}tj|ƒ}|r=|j||ƒn|j||ƒdS(N(RUtsplitt	transportt
get_transportt_dump_raw_bytest
_dump_entries(RŒRºR»tdirnametbasenamett((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRòs
cC@sOtj||dƒ}|j|ƒ}tj|ƒ|_t|ƒ|_||fS(s'Create a BTreeGraphIndex and raw bytes.N(	tbtree_indextBTreeGraphIndexRt	get_bytest	cStringIOtStringIOt_fileRbt_size(RŒttransRÂtbttbytes((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_get_index_and_bytesús
c
C@s<ddl}|j||ƒ\}}xttdt|ƒtjƒƒD]î\}}t|tjt|ƒƒ}|||!}	|dkrÉ|jj	dƒ|j
|	ƒ\}
}|jj	|	|
 ƒ|}	n|jj	d|fƒt|	ƒdkr|jj	dƒqF|j|	ƒ}|jj	|ƒ|jj	dƒqFWdS(NisRoot node:
s	
Page %d
s(empty)
s
(tzlibRÎt	enumeratetxrangeRbRÄt
_PAGE_SIZEtminR‹R£t_parse_header_from_bytest
decompress(
RŒRËRÂRÏRÌRÍtpage_idxt
page_starttpage_endt
page_bytest
header_endtdatatdecomp_bytes((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¿s"
	c
C@sày|j|ƒ}Wn,tjk
rA|j||ƒ\}}nXtj|||jƒ}x|jƒD]q}y|d}Wntk
r”d}nXt
j|ƒ}t|dƒ|d|f}	|j
jd|	fƒqgWdS(Niiis%s
(R~RtTransportNotPossibleRÎRÄRÅtst_sizetiter_all_entriest
IndexErrorRtstatic_tuplet	as_tuplesttupleR‹R£(
RŒRËRÂR}RÌt_tnodetrefstrefs_as_tuplestas_tuple((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÀs
(R‘R’R“RGR¶R—R”RR•R!RRÎR¿RÀ(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¸Üs				tcmd_remove_treecB@sDeZdZddgZdgZedddƒgZed„ZRS(sàRemove the working tree from a given branch/checkout.

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

    To re-create the working tree, use "bzr checkout".
    tcheckouts
working-treess	location*tforceRxsFRemove the working tree even if it has uncommitted or shelved changes.cC@s%|sdg}nx|D]}tjj|ƒ}y|jƒ}WnQtjk
rltjtdƒƒ‚n)tjk
r”tjtdƒƒ‚nX|sæ|j	ƒr¹tj
|ƒ‚n|jƒjƒdk	rætj|ƒ‚qæn|j|jjkrtjtdƒƒ‚n|jƒqWdS(NR;sNo working tree to removes3You cannot remove the working tree of a remote paths>You cannot remove the working tree from a lightweight checkout(RRR R"RR#RcRZR$thas_changestUncommittedChangestget_shelf_managert
last_shelfRtShelvedChangesRIR-tdestroy_workingtree(RŒt
location_listRëR5tdtworking((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR@s$
(	R‘R’R“R˜R”RR•R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRé0s		tcmd_repair_workingtreecB@sAeZdZddedddƒgZeZdded„Z	RS(	s±Reset the working tree state file.

    This is not meant to be used normally, but more as a way to recover from
    filesystem corruption, etc. This rebuilds the working inventory back to a
    'known good' state. Any new modifications (adding a file, renaming, etc)
    will be lost, though modified files will still be detected as such.

    Most users will want something more like "bzr revert" or "bzr update"
    unless the state file has become corrupted.

    By default this attempts to recover the current state by looking at the
    headers of the state file. If the state file is too corrupted to even do
    that, you can supply --revision to force the state of the tree.
    RjRrRëRxs9Reset the tree even if it doesn't appear to be corrupted.R;c
C@stj|ƒ\}}|j|jƒjƒ|sny|jƒWntjk
rUqnXtjt	dƒƒ‚n|dkrƒd}n%g|D]}|j|jƒ^qŠ}y|j
|ƒWnUtjk
r}|dkrét	dƒ}	nd}	tjt	dƒj|	ƒƒ‚nXdS(Ns‘The tree does not appear to be corrupt. You probably want "bzr revert" instead. Use "--force" if you are sure you want to reset the working tree.sS, the header appears corrupt, try passing -r -1 to set the state to the last commitRƒs!failed to reset the tree state{0}(RPRQtadd_cleanuptlock_tree_writeR°tcheck_stateRtBzrErrorRcRZRR¯R-treset_stateR®(
RŒRjRrRëR\Rätrevision_idstrtetextra((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRrs&		%N(
R‘R’R“RR•RGR¶RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRõ[s	t	cmd_revnocB@sPeZdZdgZdgZedddƒdgZeedd	d„ƒZ
RS(
s`Show current revision number.

    This is equal to the number of revisions on this branch.
    tinfos	location?R\RxsShow revno of working tree.Rju.c	C@sŠ|dk	r*|r*tjtdƒƒ‚n|r¤y-tj|ƒd}|j|jƒjƒWn,tj	tj
fk
r‹tj	|ƒ‚nX|j}|jƒ}n{t
j|ƒd}|j|jƒjƒ|rt|ƒdkrýtjtdƒƒ‚n|dj|ƒ}n|jƒ}y|j|ƒ}Wntjk
rNd	}nXdjd„|Dƒƒ}|jƒ|jj|dƒdS(
Ns.--tree and --revision can not be used togetheriisARevision numbers only make sense for single revisions, not rangess???R;cs@s|]}t|ƒVqdS(N(tstr(t.0tn((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pys	<genexpr>¹ss
(s???(RRRcRZRPRQRöR¬R°R#R$R-t
last_revisionR9RbR¯trevision_id_to_dotted_revnoR¡R4tcleanup_nowR‹R£(	RŒR\R5RjR*R²R¥trevno_ttrevno((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRœs2		

N(R‘R’R“R˜R”RR•RR!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÿs			tcmd_revision_infocB@s_eZdZeZdgZdedddƒedddƒgZe	d
degd	„ƒZRS(sJShow revision number and revision id for a given revision identifier.
    srevision_info*RjRrRxsHBranch to examine, rather than the one containing the working directory.R\sShow revno of working tree.u.c@s0y6tj|ƒd}|j‰|j|jƒjƒWnLtjtjfk
r„d}t
j|ƒd‰|jˆjƒjƒnXg}|dk	r·|j‡fd†|Dƒƒn|dk	rüx6|D]+}tj
|ƒ}|j|jˆƒƒqÊWnt|ƒdkr^|rH|dkr2tj|ƒ‚n|j|jƒƒq^|jˆjƒƒng}	d}
x|D]w}y,ˆj|ƒ}djd„|Dƒƒ}
Wntjk
r¿d}
nXt|
t|
ƒƒ}
|	j|
|gƒqqW|jƒx3|	D]+}|jjd|
|d|dfƒqýWdS(Nic3@s|]}|jˆƒVqdS(N(R¯(RR´(R²(s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pys	<genexpr>ÙsR;cs@s|]}t|ƒVqdS(N(R(Rti((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pys	<genexpr>ìss???s%*s %s
i(RPRQR-RöR¬R°RR#R$RR9textendtRevisionSpectfrom_stringtappendR¯RbRRR4R¡tmaxRR‹R£(RŒRjRrR\trevision_info_listR*Rûtrev_strtrev_spectrevinfostmaxlenR±tdotted_revnoRtri((R²s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRËsD	 




N(
R‘R’R“RGR¶R”RRR•RRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR	¾s			tcmd_addc	B@s€eZdZdgZedddddƒedddƒd	ed
deddƒgZd
ZddgZe	e	e	dd„ZRS(s´Add specified files or directories.

    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.

    A warning will be printed when nested trees are encountered,
    unless they are explicitly ignored.

    Therefore simply saying 'bzr add' will version all files that
    are currently unknown.

    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.

    --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.
    
    Any files matching patterns in the ignore list will not be added
    unless they are explicitly mentioned.
    
    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.
    sfile*s
no-recurseRxs2Don't recursively add the contents of directories.RytNsdry-runs8Show what would be done, but don't actually do anything.Rvs
file-ids-fromttypesLookup file ids from this tree.RtremovetignorecC@s“ddl}d}|dk	ršytj|ƒ\}}Wn5tjk
rntj|ƒ\}	}|	jƒ}nX|jj	||d|j
dtƒƒ}
n"|jjd|j
dtƒƒ}
|rÛ|j
|jƒjƒnt|ƒ\}}|j||d|
d|ƒ\}}
|jƒt|
ƒdkr|rxTt|
jƒƒD]=}x4|
|D](}|j
jtdƒj||ƒƒqYWqHWqndS(NiR†tshould_printtactiontsavesignored {0} matching "{1}"
(t
bzrlib.addRRPRQRR#R9RgtaddtAddFromBaseActionR‹R
tAddWithSkipLargeActionRöR¬R°Rat	smart_addRRbtsortedtkeysR£RZR®(RŒR[t
no_recursetdry_runRvt
file_ids_fromtbzrlibt	base_treet	base_pathtbase_branchRR\taddedtignoredtglobRº((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR2s6
	
	N(R‘R’R“R”RtunicodeR•R—R˜R!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR÷s+					t	cmd_mkdircB@sbeZdZdgZedddddƒgZdZed„ƒZed	„ƒZ	e
d
„ZRS(slCreate a new versioned directory.

    This is equivalent to creating the directory and then adding it.
    sdir+tparentsRxs8No error if existing, make parent directories as needed.RytpRcC@sF|j|ƒdk	rdS|j|tj|ƒƒ|j|gƒdS(N(tpath2idRtadd_file_with_parentsRURÁR (tclsR*R]((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR5escC@s|j|gƒdS(N(R (R6R*R]((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytadd_file_singlelscC@sÍ|r|j}n	|j}x«|D]£}tj|ƒ\}}|r…ytj|ƒWq’tk
r}|jtjkr‚‚q‚q’Xn
tj	|ƒ|||ƒt
ƒs"|jjt
dƒ|ƒq"q"WdS(Ns	added %s
(R5R7RPRQtostmakedirstOSErrorterrnotEEXISTtmkdirR
R‹R£RZ(RŒtdir_listR2tadd_filetdirR*R]Rý((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRps	



	(R‘R’R“R”RR•R—tclassmethodR5R7R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR1Us	tcmd_relpathcB@s,eZdZdgZeZed„ƒZRS(s$Show path of a file relative to rootR_cC@s9tj|ƒ\}}|jj|ƒ|jjdƒdS(Ns
(RPRQR‹R£(RŒR_R\R]((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRŠs(R‘R’R“R”RGR¶RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRB„s	t
cmd_inventorycB@sbeZdZeZdgZddeddddeƒgZdgZ	e
d
ed
d
d	„ƒZ
RS(s7Show inventory of the current working copy or a revision.

    It is possible to limit the output to a particular entry
    type using the --kind option.  For example: --kind file.

    It is also possible to restrict the list of files to a specific
    set. For example: bzr inventory --show-ids this/file
    tlsRjsshow-idstkindRxs<List entries of a particular kind: file, directory, symlink.Rsfile*cC@s©|r1|dkr1tjtdƒ|fƒ‚ntd|ƒ}tj|ƒ\}}|j|jƒjƒ|dk	r«|j
|jƒ}|g}|j|jƒjƒn|}g}|j|jƒjƒ|dk	r	|j|d|dt
ƒ}|jd|ƒ}	n|jƒ}	xt|	ƒD]\}
}|rI||jkrIq"n|
d	kr[q"n|r|jjd
|
|jfƒq"|jj|
ƒ|jjdƒq"WdS(
NtfileRrtsymlinksinvalid kind %r specifiedt	inventoryttreestrequire_versionedtspecific_file_idsRƒs	%-50s %s
s
(sfiles	directoryssymlink(RRcRZRfRPRŠRöR¬R°RRhR-t	paths2idsRGtiter_entries_by_dirR$RER‹R£tfile_id(RŒRjR„RER[t	work_treeR\textra_treestfile_idstentriesRºtentry((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¨s4		 N(R‘R’R“RGR¶R˜RR0R•R”RRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRC“s			tcmd_mvcB@s€eZdZdgZedddƒedddƒedddƒgZd	d
gZdZeeed„Z	d
„Z
d„ZRS(s˜Move or rename a file.

    :Usage:
        bzr mv OLDNAME NEWNAME

        bzr mv SOURCE... DESTINATION

    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 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.

    Files cannot be moved between branches.
    snames*tafterRxsRMove only the bzr identifier of the file, because the file has already been moved.tautosAutomatically guess renames.sdry-runs+Avoid making changes when guessing renames.tmovetrenameRcC@sý|r|j|||ƒS|r7tjtdƒƒ‚n|dkrLg}nt|ƒdkrvtjtdƒƒ‚ntj|dtƒ\}}x9|dd!D]*}|dkrŸtjtdƒƒ‚qŸqŸW|j	|j
ƒjƒ|j||||ƒdS(	Ns--dry-run requires --auto.ismissing file argumenttcanonicalizeiiÿÿÿÿRƒscan not move root of branch(
trun_autoRRcRZRRbRPRŠR!RöR÷R°t_run(RŒt
names_listRURVR'R\t	rel_namest	file_name((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRís	cC@sœ|dk	r6t|ƒdkr6tjtdƒƒ‚n|rTtjtdƒƒ‚ntj|ddƒ\}}|j|jƒj	ƒt
jj||ƒdS(Nis)Only one path may be specified to --auto.s(--after cannot be specified with --auto.tdefault_directoryR;(
RRbRRcRZRPRŠRöR÷R°t
rename_mapt	RenameMapt
guess_renames(RŒR\RUR'ROR[((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRZýscC@s‘tj|dƒ}|rµt|ƒdkrµ|jr^|djƒ|djƒkr^t}qµ|j|j|dƒƒ}tj|dƒrµ|rµ|j	|ƒdkrµt}qµn|r$|j
|ƒ}xÀ|j|d |dd|ƒD]2\}}tƒsë|j
jd||fƒqëqëWnit|ƒdkrNtjtdƒƒ‚n|j|dƒ}|j|dƒ}	tj|	ƒ}
tj|dƒ}|j|	ƒ}|dksÆ|j|ƒ|kr|r|
rêtj|j|
ƒ}
n	|j}
tj|
tj|
|ƒƒ}q/|}ntjj|	ƒ}tj|
|ƒ}td	||ƒ|j||d|ƒtƒs|j
jd||fƒndS(
NiÿÿÿÿiiiRrRUs	%s => %s
sBto mv multiple files the destination must be a versioned directorysattempting to move %s => %s(RUtisdirRbtcase_sensitivetlowerR!R4tget_canonical_inventory_pathtlexistststored_kindtget_canonical_inventory_pathsRWR
R‹R£RRcRZRÁRÂRtpathjointbasedirtcanonical_relpathR8RºR
t
rename_one(RŒR\R\R]RUt
into_existingtfrom_idtsrctdestt
canon_desttdest_parentt	spec_tailtdest_idtdest_parent_fqt	dest_tail((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR[	sJ
 	-	$!			(R‘R’R“R”RR•R–R—R!RRZR[(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRTÏs		tcmd_pullcB@seZdZddddgZdddedd	d
ƒedd	dƒed
d	dƒedd	dƒedd	dƒgZdgZdZdde
de
de
e
e
d„	ZRS(s(Turn this branch into a mirror of another branch.

    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.

    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.

    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.

    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.

    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>.

    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.
    tpushtupdatesstatus-flagstsendtremembert	overwriteRjRvRxsShow logs of pulled revisions.RrsJBranch to pull into, rather than the one containing the working directory.tlocalsZPerform a local pull in a bound branch.  Local pulls are not applied to the master branch.s	show-bases%Show base revision text in conflicts.soverwrite-tagssOverwrite tags only.s	location?Rc
	C@s£|rddg}n|	r'dg}ng}d}
d}|dkrNd}ny6tj|ƒd}|j}
|j|jƒjƒWn\tjk
râd}t	j|ƒd}
|j|
jƒjƒ|rãt
tdƒƒqãnX|r|
jƒrtj
ƒ‚ng}|dk	rPytj|d|ƒ}WqPtjk
rLd}qPXn|
jƒ}|dkrÓ|dkrŒtjtdƒƒ‚qÓtj||jjƒ}tƒsÊ|jjtdƒ|ƒn|}ntd	|ƒ}|dk	rF|dk	rtjtd
ƒƒ‚n|j|
jƒ|j|
jƒ\}}
}|
}nbt	j|d|ƒ}|j|jƒjƒ|s•|dkr¨|
jƒdkr¨|
j|j ƒn|dk	rÆ|j!|ƒ}
n|dk	r t"|ƒ}t#j$d|j%d|ƒ}|j&|||
|d
|d|ƒ}n|
j&|||
d
|ƒ}|j'|jƒ|r…|j(|j)kr…t*j+|
|j|j,|j(ƒnt-|ddƒr›dSdSdS(Nthistoryttagsu.is%No working tree, ignoring --show-baseRs$No pull location known or specified.s Using saved parent location: %s
tpulls.Cannot use -r with merge directives or bundlestunversioned_filterRnR~t	show_baset
tag_conflictsi(.RRPRQR-Röt
lock_writeR°RR#R9RRZRtLocalRequiresBoundBranchtbundletread_mergeable_from_urlt
NotABundlet
get_parentRcR1tunescape_for_displayR‹R·R
R£Rftinstall_revisionsR«tget_merge_requestR R¬t
set_parentRR¯Rptdeltat_ChangeReportert
is_ignoredRtreportt	old_revidt	new_revidtlogtshow_branch_changet	old_revnotgetattr(RŒR5R|R}RjRvRrR~Rƒtoverwrite_tagsR±t	mergeablettree_tot	branch_toRt
stored_loctdisplay_urltbase_revision_idtverifiedtbranch_fromRntchange_reportertresult((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR‹sŽ		

									
N(R‘R’R“R˜RRR•R”R—RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRxYs&								tcmd_pushcB@sìeZdZdddgZddddedd	d
ƒedd	dƒed
d	dƒedd	dƒedd	ddeƒedd	dƒedd	dƒedd	dƒgZdgZdZ	ddeeededdedeed„
ZRS(sQUpdate a mirror of this branch.

    The target branch will not have its working tree populated because this
    is both expensive, and is not supported on remote file systems.

    Some smart servers or protocols *may* put the working tree in place in
    the future.

    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.

    If branches have diverged, you can use 'bzr push --overwrite' to replace
    the other branch completely, discarding its unmerged changes.

    If you want to ensure you have the different changes in the other branch,
    do a merge (see bzr help merge) from the other branch, and commit that.
    After that you will be able to do a push without '--overwrite'.

    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.

    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>.
    RRzs
working-treesR|R}RvRjs
create-prefixRxsFCreate the path leading up to the branch if it does not already exist.RrsJBranch to push from, rather than the one containing the working directory.suse-existing-dirsBy default push will fail if the target directory exists, but does not already have a control directory.  This flag will allow push to proceed.tstackedsQCreate a stacked branch that references the public location of the parent branch.s
stacked-ons£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.RRšsdRefuse to push if there are uncommitted changes in the working tree, --no-strict disables the check.sno-treesDDon't populate the working tree, even for protocols that support it.soverwrite-tagssOverwrite tags only.s	location?RcC@sSddlm}|r%ddg}n|
r7dg}ng}|dkrRd}ntjj|ƒ\}}}td|ƒ}|dk	r|j|ƒj}nd}|dk	rÚ|dkrÚ|j	|ddd	d
dƒn|	dk	røt
j|	ƒ}	nf|
r^|jƒ}|r=t
j|ƒ}|jƒ}	|	s=|}	q=n|	s^tjtdƒƒ‚q^n|dkr|jƒ}|dkrÚ|jƒ}|rÂtjtd
t
j||jjƒƒƒ‚qtjtdƒƒ‚qt
j||jjƒ}ttdƒ|ƒ|}n|||||jd|d|d|d|	d|d|d|ƒdS(Ni(t_show_push_branchRR€R;Rytpush_strictt
more_errors"Use --no-strict to force the push.tmore_warnings'Uncommitted changes will not be pushed.s'Could not determine branch to refer to.sbNo push location known or specified. To push to the parent branch (at %s), use 'bzr push :parent'.s$No push location known or specified.sUsing saved push location: %sRvR}R|t
stacked_ont
create_prefixtuse_existing_dirtno_tree(tbzrlib.pushR¦RRRRqRft
in_historyRµtcheck_changed_or_out_of_dateR1t
normalize_urlRŠR9R tget_public_branchRRcRZtget_push_locationR‹R‹R·R(RŒR5R|R}R«RvRjR¬RrRªR¥RšRR™R¦R\tbr_fromt_unusedR±t
parent_urltparentRt
parent_locRž((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR*sb		
						N(
R‘R’R“R˜RRR0R•R”R—RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¤ës6													t
cmd_branchcB@sÝeZdZdgZddgZdedddƒedd	edd
ƒedddƒed
ddƒedddƒedddƒedddƒedddƒg	ZddgZdde
e
e
e
e
e
e
dd„
ZRS(s™Create a new branch that is a copy of an existing branch.

    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.

    To retrieve the branch as of a particular revision, supply the --revision
    parameter, as in "branch foo/bar -r 5".

    The synonyms 'clone' and 'get' for this command are deprecated.
    Rêt
from_locationsto_location?RjthardlinkRxs,Hard-link working tree files where possible.s
files-fromRs!Get file contents from this tree.sno-trees'Create a branch without a working-tree.tswitchs?Switch the checkout in the current directory to the new branch.R¥sCreate a stacked branch referring to the source branch. The new branch will depend on the availability of the source branch for all operations.t
standalones2Do not use a shared repository, even if available.suse-existing-dirs“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.tbinds!Bind new branch to from location.tgettclonecC@sQddlm}ddlm}
|jdkrWtjjdd|jdd	d
dƒntj	j
|ƒ\}}|px|s„d}n|dk	r®||kr®tj
|ƒ}ntd	|ƒ}|j|jƒjƒ|dk	rñ|j|ƒ}n|jƒ}|dkr6t|ddƒ}|s6tj|ƒ}q6ntj|ƒ}y|jd
ƒWnÉtjk
rõytj	j|ƒ}Wn<tjk
r½|s´tjtdƒ|ƒ‚qòd}q(Xy|j ƒWntjk
râq(Xtj!|ƒ‚n3tj"k
r!tjtdƒ|ƒ‚nXd}|dkrêyh|j#j$|j%|d|gd|d|d|d|d|d|ƒ}|j d|j#j&|gƒ}WqHtj'k
ræ|j(d
ƒtdƒj)||ƒ}tj|ƒ‚qHXn^y|j*ƒ}Wn tj+k
r|j,ƒ}nX|j-|j.d|ƒ|j$|d|ƒ}|
||ƒyt/tdƒ|j0ƒƒWnKtj1tj2tj3fk
rÀ}t/t4dd|j5ƒƒ|j5ƒƒnX|
rút6j
|ƒ}|j7|ƒt/tdƒ|ƒn|	rMtj8d
ƒ\}}|j|j#|ƒt/tdƒtj9|j%dƒƒndS( Ni(R¼(t_merge_tags_if_possibleR¿RÀtdeprecated_commandtdeprecated_nametrecommended_nameR-tdeprecated_in_versions2.4RCR;s%Target directory "%s" already exists.sParent of "%s" does not exist.Rtaccelerator_treeR»R¥tforce_new_repotcreate_tree_if_localt
source_branchs#The branch {0} has no revision {1}.R±s+Created new stacked branch referring to %s.sBranched %d revision.sBranched %d revisions.sNew branch bound to %ssSwitched to branch: %ssutf-8(sgetRÀ(:R)R¼t
bzrlib.tagRÁt
invoked_astuit
ui_factorytshow_user_warningRRtopen_tree_or_branchRRPR RfRöR¬R°R¯RR˜R1tderive_to_locationR½R¾R=Rt
FileExiststopen_from_transportRRcRZRtAlreadyBranchErrort
NoSuchFileRDtsproutRRR¡tdelete_treeR®topen_repositorytNoRepositoryPresenttcreate_repositorytfetchR«Rtget_stacked_on_urlt
NotStackedtUnstackableBranchFormattUnstackableRepositoryFormattngettextRR9R¾RQR‹(RŒRºtto_locationRjR»R¥R½RR¬R¼R¾t
files_fromt_mod_switchRÁRÆR´R±tto_transporttto_dirR-R³tto_repoRýt
parent_branchR*Rä((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRŸs¤		
			

			


*
N(R‘R’R“R˜R”RRR•R–RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¹ts0								tcmd_branchescB@sAeZdZdgZedddddƒgZded„ZRS(	s‘List the branches available at the current location.

    This command will print the names of all the branches at the current
    location.
    s	location?t	recursiveRytRRxsQRecursively scan for branches rather than just looking in the specified location.R;cC@sß|r”tj|ƒ}|jƒs3tjdƒ‚nx¥tjj|ƒD]G}|jj	dt
jt
j|j
|j
ƒ|jjƒjdƒƒqFWnGtjj|ƒd}y|jddƒ}Wntjk
rÜd}nXi}xTt|ƒD]F\}}	|dkrqðn|dk	o)|j
|	j
k}
|
||<qðWt|jƒƒrv|dk	rv|jj	dtdƒƒnxbt|jƒƒD]N}||}
|
r¨d	}nd
}|jj	d||j|jjƒfƒq‰WdS(Ns!Can't scan this type of location.s%s
R,iRCRƒs* %s
s	(default)t*t s%s %s
(R½R¾tlistableRRcRRRFR‹R£R1R‹RHRR·RJRQRRRROtanytvaluesRZR$R%tencode(RŒR5RèRÃR²R@t
active_branchtnamesRCR-tactivetprefix((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs<!

	(R‘R’R“R”RR•R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRç
s
	tcmd_checkoutcB@sŒeZdZddddgZddgZdedd	d
ƒedded	d
ƒedd	dƒgZdgZddde
de
d„ZRS(sÜCreate a new checkout of an existing branch.

    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 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.

    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.)
    t	checkoutsR-s
working-treessremove-treesbranch_location?sto_location?RjtlightweightRxsä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.s
files-fromRs!Get file contents from this tree.R»s,Hard-link working tree files where possible.tcoc
C@s@|dkr!tjƒ}|}ntjj|ƒ\}}|pB|sNd}ntd|ƒ}|dk	r‡||kr‡tj|ƒ}n|dk	r¥|j	|ƒ}	nd}	|dkrÉt
j|ƒ}ntj|ƒtj|ƒkr#y|j
jƒWq#tjk
r|j
j|	ƒdSXn|j||	|||ƒdS(NRê(RRUtgetcwdRRRÏRfRPR R¯R1RÐRXRDR"RR#tcreate_workingtreetcreate_checkout(
RŒtbranch_locationRàRjRöRáR»RÆtsourceR±((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRcs0			N(R‘R’R“R˜R”RRR•R–RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRô<s				tcmd_renamescB@s2eZdZdgZdgZedd„ƒZRS(s Show list of renamed files.
    tstatussdir?u.c	C@stj|ƒd}|j|jƒjƒ|jƒ}|j|jƒjƒg}|j|dtƒ}x_|D]W\}}}}	}
}}}
|d|dkr¥qmnd|kr·qmn|j	|ƒqmW|j
ƒx.|D]&\}}|jjd||fƒqÙWdS(Nitinclude_unchangedis	%s => %s
(
RPRQRöR¬R°Rgtiter_changesRGRRtsortR‹R£(RŒR@R\told_treetrenamestiteratortftpathstctvR3RtkRýtold_nametnew_name((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs%
(R‘R’R“R˜R”RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRý†s
		t
cmd_updatecB@sYeZdZdddgZdgZdedddƒgZd	gZdddd
„Z	RS(svUpdate a working tree to a new revision.

    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.  

    You can use this to visit an older revision, or to update a working tree
    that is out of date from its branch.
    
    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 'bzr revert'.  The uncommitted changes may conflict
    with the changes brought in by the change in basis revision.

    If the tree's branch is bound to a master branch, bzr will also update
    the branch from the master.

    You cannot update just a single file or directory, because each Bazaar
    working tree has just a single basis revision.  If you want to restore a
    file that has been removed locally, use 'bzr revert' instead of 'bzr
    update'.  If you want to restore a file to its state in a previous
    revision, use 'bzr revert' with a '-r' option, or use 'bzr cat' to write
    out the old content of that file to a new location.

    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.
    Rs
working-treessstatus-flagssdir?Rjs	show-baseRxs%Show base revision text in conflicts.tupc
C@sú|dk	r6t|ƒdkr6tjtdƒƒ‚n|dkrXtjdƒd}n3tj|ƒ\}}|r‹tjtdƒƒ‚n|j}g}|jd|ƒ}|dk	rÎ|j	}	|j
ƒn|jj	}	|jƒ|j|j
ƒtj|	jdƒ|jjƒ}	|jƒd}
|dkr:d}n|j|ƒ}|dk	rk|dj|ƒ}n|jƒ}|tj|jƒƒkrÓ|j|ƒ}
ttdƒjdjtt|
ƒƒ|	ƒƒdSt|ƒ}t j!d	|j"d
|ƒ}y+|j|d|d|d|d
|ƒ}Wn2tj#k
rY}tjtdƒ|j$ƒ‚nX|jjtj|jƒƒƒ}
ttdƒjdjtt|
ƒƒ|	ƒƒ|jƒ}|drâ|d|
krâttdƒƒn|dkròdSdSdS(Nis0bzr update --revision takes exactly one revisionR;isCbzr update can only update a whole tree, not a file or subdirectoryRR,s0Tree is up to date at revision {0} of branch {1}R‚RnRjtold_tipRƒs_branch has no revision %s
bzr update --revision only works for a revision in the branch historys%Updated to revision {0} of branch {1}smYour local commits will now show as pending merges with 'bzr status', and can be committed with 'bzr commit'.(%RRbRRcRZRPRQR-tget_master_branchRR…R÷RöR°R1R‹RJR‹R·tget_parent_idsRzR¯Rt
_mod_revisiontensure_nullRRR®R4tmapRRpRRR‘R¡Rj(RŒR@RjRƒR\R]R-RtmasterRûtexisting_pending_mergesRR±RRnR¢t	conflictsRýt
parent_ids((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÈsv						

				
		N(
R‘R’R“R˜R”RR•R–RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¢s			tcmd_infocB@sJeZdZdddgZdgZdgZdZede	d„ƒZ
RS(	ssShow information about a working tree, branch or repository.

    This command will show all known locations and formats associated to the
    tree, branch or repository.

    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.

    Branches and working trees will also report any missing revisions.

    :Examples:

      Display information on the format and related locations:

        bzr info

      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):

        bzr info -v

      Display the above together with number of committers to the branch:

        bzr info -vv
    Rs
working-treestrepositoriess	location?RvRcC@sU|rtƒ}nd}ddlm}|tjj|ƒdd|d|jƒdS(Ni(tshow_bzrdir_infoRvtoutfile(Rtbzrlib.infoRRRRQR‹(RŒR5Rvtnoise_levelR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR5sN(R‘R’R“R˜R”R•R—RRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs		t
cmd_removecB@s†eZdZdgZdedddƒejdddd	d
ededd
ddddƒgZ	ddgZ
dZeedd„ZRS(sŸRemove files or directories.

    This makes Bazaar stop tracking changes to the specified files. Bazaar will
    delete them if they can easily be recovered using revert otherwise they
    will be backed up (adding an extension of the form .~#~). If no options or
    parameters are given Bazaar will scan for files that are being tracked by
    Bazaar but missing in your tree and stop tracking them for you.
    sfile*RvtnewRxs1Only remove files that have never been committed.sfile-deletion-strategys"The file deletion mode to be used.ttitlesDeletion Strategytvalue_switchestenum_switchtsafesBackup changed files (default).tkeeps+Delete from bzr but leave the working copy.t	no_backupsDon't backup changed files.trmtdelRc
C@s’tj|ƒ\}}|dk	r=g|D]}|^q(}n|j|jƒjƒ|rÍ|j|jƒd|ƒj}t	g|D]}|d^qdt
ƒ}t|ƒdkrZtj
tdƒƒ‚qZn|dkrZg}x]|j|jƒƒD]F}	|	dddk	rõ|	dddkrõ|j|	ddƒqõqõWt	|dt
ƒ}d}n|j|d|d	|jd
|dkd|dkƒdS(
NR…itreversesNo matching files.iiR$RvR†t
keep_filesRës	no-backup(RPRŠRRöR…R°tchanges_fromRgR-R$RGRbRRcRZRRRR‹(
RŒR[RvRtfile_deletion_strategyR\RR-tmissingRu((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRVs()(	(
R‘R’R“R”RRtfrom_kwargsRGR!R•R–R—R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR@s		tcmd_file_idcB@s8eZdZeZddgZdgZed„ƒZRS(sÛPrint file_id of a particular file or directory.

    The file_id is assigned when the file is first added and remains the
    same through all revisions where the file exists, even when it is
    moved or renamed.
    RHRDR_cC@sZtj|ƒ\}}|j|ƒ}|dkrBtj|ƒ‚n|jj|dƒdS(Ns
(RPRQR4RRtNotVersionedErrorR‹R£(RŒR_R\R]R
((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR‚s
(	R‘R’R“RGR¶R˜R”RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR.vs
	t
cmd_file_pathcB@s,eZdZeZdgZed„ƒZRS(s•Print path of file_ids to a file or directory.

    This prints one line for each directory down to the target,
    starting at the branch root.
    R_cC@s©tj|ƒ\}}|j|ƒ}|dkrBtj|ƒ‚ntj|ƒ}xQtdt	|ƒdƒD]6}tj
|| ƒ}|jjd|j|ƒƒqkWdS(Nis%s
(
RPRQR4RRR/RUt	splitpathtrangeRbtjoinpathR‹R£(RŒR_R\R]tfidtsegmentstposRº((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR–s (R‘R’R“RGR¶R”RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR0Œs	t
cmd_reconcilecB@sJeZdZdgZdgZeddddeƒgZded„Z	RS(	sºReconcile bzr metadata in a branch.

    This can correct data mismatches that may have been caused by
    previous ghost operations or bzr upgrades. You should only
    need to run this command if 'bzr check' or a bzr developer
    advises you to run it.

    If a second branch is provided, cross-branch reconciliation is
    also attempted, which will check that data like the tree root
    id which was not present in very early bzr versions is represented
    correctly in both branches.

    At the same time it is run it may recompress data resulting in
    a potential saving in disk space or performance gain.

    The branch *MUST* be on a listable system such as local disk or sftp.
    tchecksbranch?scanonicalize-chksRxs:Make sure CHKs are in canonical form (repairs bug 522637).R¶R;cC@s6ddlm}tjj|ƒ}||d|ƒdS(Ni(t	reconciletcanonicalize_chks(tbzrlib.reconcileR9RRR (RŒR-R:R9R@((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¾s(
R‘R’R“R˜R”RRGR•R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR7¢s			tcmd_revision_historycB@s8eZdZdgZdgZeZedd„ƒZRS(s-Display the list of revision ids on a branch.R•s	location?R;cC@s—tj|ƒd}|j|jƒjƒ|jjƒ}t|j|j	ƒt
jgƒƒ}x4t|ƒD]&}|j
j|ƒ|j
jdƒqiWdS(Nis
(R9RQRöR¬R°R«t	get_graphtlisttiter_lefthand_ancestryRRt
NULL_REVISIONtreversedR‹R£(RŒR5R-tgraphRR¥((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÌs(	R‘R’R“R˜R”RGR¶RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR<Äs		tcmd_ancestrycB@s;eZdZddgZdgZeZedd„ƒZRS(s+List all revisions merged into this branch.R•srevision-historys	location?R;c
C@sõytj|ƒd}Wn/tjk
rHtj|ƒ}|jƒ}nX|j}|jƒ}|j|j	j
ƒjƒ|j	jƒ}g|j
|gƒD]\}}|^q™}x=t|ƒD]/}	tj|	ƒrÙq¾n|jj|	dƒq¾WdS(Nis
(RPRQRR#R9R RR-RöR«R¬R°R=t
iter_ancestryRARtis_nullR‹R£(
RŒR5R*R²RRBR¥R2ReR±((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRàs	((	R‘R’R“R˜R”RGR¶RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRCØs	tcmd_initc
B@s˜eZdZdddgZdgZedddƒeddd	d
dd
d„deddƒedddƒeddƒgZdde
e
e
d„ZRS(s™Make a directory into a versioned branch.

    Use this to create an empty branch, or before importing an
    existing project.

    If there is a repository in a parent directory of the location, then
    the history of the branch will be stored in the repository.  Otherwise
    init creates a standalone branch which carries its own history
    in the .bzr directory.

    If there is already a branch at the location but it has no working tree,
    the tree can be populated with 'bzr checkout'.

    Recipe for importing a tree of files::

        cd ~/project
        bzr init
        bzr add .
        bzr status
        bzr commit -m "imported project"
    sinit-repositoryR-Rês	location?s
create-prefixRxsFCreate the path leading up to the branch if it does not already exist.R®s5Specify a format for this branch. See "help formats".t
lazy_registrysbzrlib.controldirtformat_registryt	convertercC@stjj|ƒS(N(RRHtmake_bzrdir(RC((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt<lambda>sR!R s
Branch formatsappend-revisions-onlysFNever change revnos or the existing log.  Append revisions to it only.sno-trees'Create a branch without a working tree.cC@sÿ|dkr!tjjdƒ}n|dkr6d}ntj|ƒ}y|jƒWn@tjk
r•|sˆtj	t
dƒ|ƒ‚n|jƒnXytjj
|ƒ}Wnbtjk
rtjj}|rÚt}	nd}	||jd|d|gd|	ƒ}
|
j}nŠXddlm}|jƒrmt||ƒr[|jƒr[tj|ƒ‚ntj|ƒ‚n|jƒ}
|rš|jƒrš|jƒn|rày|
jtƒWqàtjk
rÜtj	t
d	ƒƒ‚qàXntƒsûdd
l m!}m"}
y|j#dtƒ}Wn#tj$tj%fk
r:d}nX|
j&}|||
|ƒj'ƒ}|
|||
|ƒ}|j(j)t
dƒj*||ƒƒ|j+ƒrû|jj,j-ƒ}yt.j/|ƒ}Wntj0k
rÚnX|j(j)t
d
ƒ|ƒqûndS(Ntdefaultu.soParent directory of %s does not exist.
You may supply --create-prefix to create all leading parent directories.R®Rtforce_new_treei(tLocalTransportsJThis branch format cannot be set to append-revisions-only.  Try --default.(tdescribe_layouttdescribe_formattrecommend_upgradesCreated a {0} (format: {1})
sUsing shared repository: %s
(1RRRHRJR½R¾tensure_baseRRÔRcRZR«RRÒRtcreate_branch_convenienceR!RRDtbzrlib.transport.localRNt
has_brancht
isinstancethas_workingtreetBranchExistsWithoutWorkingTreeRÓt
create_branchRùtset_append_revisions_onlyRGtUpgradeRequiredR
RRORPR"R#R$R«ReR‹R£R®t	is_sharedRtexternal_urlR1tlocal_path_from_urlt
InvalidURL(RŒR5R®tappend_revisions_onlyR«RRãta_bzrdirRYRMR-RNRORPR\R«tlayoutturl((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR sn	
			


	
	
(sbzrlib.controldirsformat_registryN(R‘R’R“R˜R”RRRGR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRFõs"						tcmd_init_repositorycB@s€eZdZddddgZdgZedddd	ddd
„deddƒedddƒgZdgZ	ded„ZRS(s#Create a shared repository for branches to share storage space.

    New branches created under the repository directory will store their
    revisions in the repository, not in the branch directory.  For branches
    with shared history, this reduces the amount of storage needed and 
    speeds up the creation of new branches.

    If the --no-trees option is given then the branches in the repository
    will not have working trees by default.  They will still exist as 
    directories on disk, but they will not have separate copies of the 
    files at a certain revision.  This can be useful for repositories that
    store branches which are interacted with through checkouts or remote
    branches, such as on a server.

    :Examples:
        Create a shared repository holding just branches::

            bzr init-repo --no-trees repo
            bzr init repo/trunk

        Make a lightweight checkout elsewhere::

            bzr checkout --lightweight repo/trunk trunk-checkout
            cd trunk-checkout
            (add files here)
    tinitR-RêRR5R®RxsISpecify a format for this repository. See "bzr help formats" for details.RGsbzrlib.controldirRHRIcC@stjj|ƒS(N(RRHRJ(RC((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRKsR!R sRepository formatsno-treessEBranches in the repository will default to not having a working tree.s	init-repoc
C@sÇ|dkr!tjjdƒ}n|dkr6d}ntj|ƒ}|j|dtd|dtdtdtd|jj	ƒƒ\}}}}t
ƒsÃd	d
lm}	|	|dd	d|j
ƒndS(
NRLR;R«tmake_working_treestshared_repoRÇR¬trepo_format_namei(RRvR(RRRHRJR½R¾tinitialize_on_transport_exRGtrepository_formattget_format_stringR
RRR‹(
RŒR5R®tno_treesRãRNtnewdirtrequire_stackingtrepository_policyR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR•s	
	(sbzrlib.controldirsformat_registryN(
R‘R’R“R˜R”RRGRR•R–RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRdks					tcmd_diffcB@s
eZdZdgZdgZeddeddƒeddedd	dd
ƒeddddeƒed
dddeƒddeddddeƒeddddddd!ddƒedddde	ƒg	Z
ddgZdZe
d"d"d"d"d"d"d"d"d"d „	ƒZRS(#sV
Show differences in the working tree, between revisions or branches.

    If no arguments are given, all changes for the current tree are listed.
    If files are given, only the changes in those files are listed.
    Remote and multiple branches can be compared by using the --old and
    --new options. If not provided, the default for both is derived from
    the first argument, if any, or the current tree if no arguments are
    given.

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

    Note that when using the -r argument with a range of revisions, the
    differences are computed between the two specified revisions.  That
    is, the command does not show the changes introduced by the first 
    revision in the range.  This differs from the interpretation of 
    revision ranges used by "bzr log" which includes the first revision
    in the range.

    :Exit values:
        1 - changed
        2 - unrepresentable changes
        3 - error
        0 - no change

    :Examples:
        Shows the difference in the working tree versus the last commit::

            bzr diff

        Difference between the working tree and revision 1::

            bzr diff -r1

        Difference between revision 3 and revision 1::

            bzr diff -r1..3

        Difference between revision 3 and revision 1 for branch xxx::

            bzr diff -r1..3 xxx

        The changes introduced by revision 2 (equivalent to -r1..2)::

            bzr diff -c2

        To see the changes introduced by revision X::
        
            bzr diff -cX

        Note that in the case of a merge, the -c option shows the changes
        compared to the left hand parent. To see the changes against
        another parent, use::

            bzr diff -r<chosen_parent>..X

        The changes between the current revision and the previous revision
        (equivalent to -c-1 and -r-2..-1)

            bzr diff -r-2..

        Show just the differences for file NEWS::

            bzr diff NEWS

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

            bzr diff xxx/NEWS

        Show the differences from branch xxx to this working tree:

            bzr diff --old xxx

        Show the differences between two branches for file NEWS::

            bzr diff --old xxx --new yyy NEWS

        Same as 'bzr diff' but prefix paths with old/ and new/::

            bzr diff --prefix old/:new/
            
        Show the differences using a custom diff program with options::
        
            bzr diff --using /usr/bin/diff --diff-options -wu
    Rþsfile*sdiff-optionsRRxs0Pass these options to the external diff program.RóRyR3sbSet prefixes added to old and new filenames, as two values separated by a colon. (eg "old/:new/").toldsBranch/tree to compare from.RsBranch/tree to compare to.RjRuR?s"Use this command to compare files.R®tFsDiff format to use.RGsbzrlib.diffRHR sDiff formattcontexts"How many lines of context to show.tditdifR¹c
C@s…ddlm}
m}|dks.|dkr=d}d}
nT|dkrXd}d}
n9d|kr||jdƒ\}}
ntjtd	ƒƒ‚|rÁt|ƒd
krÁtjtdƒƒ‚n|dk	rý|dk	rýtjtdƒj	d
dƒƒ‚n|
|||||j
dtƒ\}}}}}}tj
ƒ}|||tjd|d|d|d|
d|d|d|d|	d|ƒ	S(Ni(t%get_trees_and_branches_to_diff_lockedtshow_diff_treest0Rƒt1sold/snew/t:sA--prefix expects two values separated by a colon (eg "old/:new/")is@bzr diff --revision takes exactly one or two revision specifierss"{0} and {1} are mutually exclusives--usings--formatt
apply_viewR…texternal_diff_optionst	old_labelt	new_labelRPt
path_encodingR?Rst
format_cls(tbzrlib.diffRvRwRR¼RRcRZRbR®RöRGRUtget_diff_header_encodingtsyststdout(RŒRjR[tdiff_optionsRóRqRR?R®RsRvRwR}R~Rtnew_treet
old_brancht
new_branchR…RPR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR#	s8					0(sbzrlib.diffsformat_registryN(R‘R’R“R˜R”RRR0RtintR•R–R—RRR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRp©sBU								tcmd_deletedcB@s;eZdZddgZddgZeedd„ƒZRS(s,List files deleted in the working tree.
    RþRDRrsshow-idsu.cC@sÍtj|ƒd}|j|jƒjƒ|jƒ}|j|jƒjƒx{|jƒD]m\}}|j|jƒsX|j	j
|ƒ|r²|j	j
dƒ|j	j
|jƒn|j	j
dƒqXqXWdS(NiRës
(RPRQRöR¬R°RgRMthas_idRNR‹R£(RŒR„RrR\RqRºtie((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR]	s(R‘R’R“R˜R•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRŠQ	s
tcmd_modifiedcB@sAeZdZeZddgZddgZeedd„ƒZ	RS(s)List files modified in working tree.
    RþRDRrtnullu.c
C@s©tj|ƒd}|j|jƒjƒ|j|jƒƒ}|jƒxZ|jD]O\}}}}}	|r„|j	j
|dƒqR|j	j
tj|ƒdƒqRWdS(Nits
(
RPRQRöR¬R°R*RgRtmodifiedR‹R£RUtquotefn(
RŒRŽRrR\ttdRºtidREt
text_modifiedt
meta_modified((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRt	s
(
R‘R’R“RGR¶R˜R•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRl	st	cmd_addedcB@sAeZdZeZddgZddgZeedd„ƒZ	RS(s&List files added in working tree.
    RþRDRrRŽu.cC@stj|ƒd}|j|jƒjƒ|jƒ}|j|jƒjƒ|jƒ}x®|jƒD] }|j|ƒrqdn||kr‘qdn|j	|ƒ}t
jtj
|j|ƒt
jƒsÊqdn|rç|jj|dƒqd|jjtj|ƒdƒqdWdS(NiRs
(RPRQRöR¬R°Rgtget_root_idtall_file_idsR‹tid2pathR8taccessRURjRktF_OKR‹R£R‘(RŒRŽRrR*tbasistroot_idRNRº((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR‰	s $(
R‘R’R“RGR¶R˜R•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR–	stcmd_rootcB@s)eZdZdgZedd„ƒZRS(sqShow the tree root directory.

    The root is the nearest enclosing directory with a .bzr control
    directory.s	filename?cC@s.tj|ƒd}|jj|jdƒdS(sPrint the branch root.is
N(RPRQR‹R£Rk(RŒR_R\((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¥	sN(R‘R’R“R”RRR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRžž	s	cC@sAyt|ƒSWn,tk
r<tdƒ}tj|ƒ‚nXdS(Ns&The limit argument must be an integer.(R‰t
ValueErrorRZRRc(tlimitstringR³((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_parse_limit¬	s

cC@sAyt|ƒSWn,tk
r<tdƒ}tj|ƒ‚nXdS(Ns'The levels argument must be an integer.(R‰RŸRZRRc(tsR³((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt
_parse_levels´	s

tcmd_logcB@seZdZdgZddgZedddƒdeddd	ƒd
dedd
ejj	ddddƒde
dddddd?ƒedddddddd
eƒedddd
ed e
ƒed!dd"dd#ddd
eƒed$dd%dd&ƒed'dd(ƒed)d e
dd*ƒed+dd,ƒed-dd.ƒed/dd0ƒed1dd2dd3d
eƒed4dd5d
eƒed6dd7d
eƒed8dd9d
eƒed:dd;d
eƒgZd<Zed@d=eeed@d@d@d@d@d@ed@d@eed@d@d@d@d@eejd>„ƒZRS(AshShow historical log for a branch or subset of a branch.

    log is bzr's default tool for exploring the history of a branch.
    The branch to use is taken from the first parameter. If no parameters
    are given, the branch containing the working directory is logged.
    Here are some simple examples::

      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 filtering, ordering and information shown for each revision can
    be controlled as explained below. By default, all revisions are
    shown sorted (topologically) so that newer revisions appear before
    older ones and descendants always appear before ancestors. If displayed,
    merged revisions are shown indented under the revision in which they
    were merged.

    :Output control:

      The log format controls how information about each revision is
      displayed. The standard log formats are called ``long``, ``short``
      and ``line``. The default is long. See ``bzr help log-formats``
      for more details on log formats.

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

        -l N        display a maximum of N revisions
        -n N        display N levels of revisions (0 for all, 1 for collapsed)
        -v          display a status summary (delta) for each revision
        -p          display a diff (patch) for each revision
        --show-ids  display revision-ids (and file-ids), not just revnos

      Note that the default number of levels to display is a function of the
      log format. If the -n option is not used, the standard log formats show
      just the top level (mainline).

      Status summaries are shown using status flags like A, M, etc. To see
      the changes explained using words like ``added`` and ``modified``
      instead, use the -vv option.

    :Ordering control:

      To display revisions from oldest to newest, use the --forward option.
      In most cases, using this option will have little impact on the total
      time taken to produce a log, though --forward does not incrementally
      display revisions like --reverse does when it can.

    :Revision filtering:

      The -r option can be used to specify what revision or range of revisions
      to filter against. The various forms are shown below::

        -rX      display revision X
        -rX..    display revision X and later
        -r..Y    display up to and including revision Y
        -rX..Y   display from X to Y inclusive

      See ``bzr help revisionspec`` for details on how to specify X and Y.
      Some common examples are given below::

        -r-1                show just the tip
        -r-10..             show the last 10 mainline revisions
        -rsubmit:..         show what's new on this branch
        -rancestor:path..   show changes since the common ancestor of this
                            branch and the one at location path
        -rdate:yesterday..  show changes since yesterday

      When logging a range of revisions using -rX..Y, log starts at
      revision Y and searches back in history through the primary
      ("left-hand") parents until it finds X. When logging just the
      top level (using -n1), an error is reported if X is not found
      along the way. If multi-level logging is used (-n0), X may be
      a nested merge revision and the log will be truncated accordingly.

    :Path filtering:

      If parameters are given and the first one is not a branch, the log
      will be filtered to show only those revisions that changed the
      nominated files or directories.

      Filenames are interpreted within their historical context. To log a
      deleted file, specify a revision range so that the file existed at
      the end or start of the range.

      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

      In this case:

      * ``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).

    :Other filtering:

      The --match option can be used for finding revisions that match a
      regular expression in a commit message, committer, author or bug.
      Specifying the option several times will match any of the supplied
      expressions. --match-author, --match-bugs, --match-committer and
      --match-message can be used to only match a specific field.

    :Tips & tricks:

      GUI tools and IDEs are often better at exploring history than command
      line tools: you may prefer qlog or viz from qbzr or bzr-gtk, the
      bzr-explorer shell, or the Loggerhead web interface.  See the Plugin
      Guide <http://doc.bazaar.canonical.com/plugins/en/> and
      <http://wiki.bazaar.canonical.com/IDEIntegration>.  

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

        [ALIASES]
        tip = log -r-1
        top = log -l10 --line
        show = log -v -p

      ``bzr tip`` will then show the latest revision while ``bzr top``
      will show the last 10 mainline revisions. To see the details of a
      particular revision X,  ``bzr show -rX``.

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

      ``bzr log -v`` on a branch with lots of history is currently
      very slow. A fix for this issue is currently under development.
      With or without that fix, it is recommended that a revision range
      be given when using the -v option.

      bzr has a generic full-text matching plugin, bzr-search, that can be
      used to find revisions matching user names, commit messages, etc.
      Among other features, this plugin can find all revisions containing
      a list of words but not others.

      When exploring non-mainline history on large projects with deep
      history, the performance of log can be greatly improved by installing
      the historycache plugin. This plugin buffers historical information
      trading disk space for faster speed.
    sfile*slog-formatstrevisionspectforwardRxsShow from oldest to newest.ttimezoneRvs$Show files changed in each revision.sshow-idsRjRuRRyRs?Show just the specified revision. See also "help revisionspec".s
log-formattauthorss8What names to list as authors - first, all or committer.R tAuthorsRGs
bzrlib.logtauthor_list_registrytlevelsRs4Number of levels to display - 0 for all, 1 for flat.targnameRtmessages=Show revisions whose message matches this regular expression.R¶tlimittls*Limit the output to the first N revisions.s	show-diffR3s.Show changes made in each revision as a patch.sinclude-mergeds+Show merged revisions like --levels 0 does.sinclude-mergess&Historical alias for --include-merged.somit-mergess0Do not report commits with more than one parent.sexclude-common-ancestrysQDisplay only the revisions that are not part of both ancestries (require -rX..Y).t
signaturess Show digital signature validity.tmatchtms6Show revisions whose properties match this expression.s
match-messages5Show revisions whose message matches this expression.smatch-committers7Show revisions whose committer matches this expression.smatch-authors3Show revisions whose authors match this expression.s
match-bugss0Show revisions whose bugs match this expression.Rtoriginalc/C@s	ddlm}m}m}|r(dp+d}tj|ƒr¡tjjddddd	d
dd|j	ƒ|
dkr}|}
q¡tjt
d
ƒjdd	ƒƒ‚n|
dkr¶t}
n|rò|dksÚt|ƒdkròtjt
dƒƒ‚n|
r1|	dkr
d}	q1tjt
d
ƒjdd	ƒƒ‚n|dk	r—t|ƒdkr^tjƒ‚n|dk	rŽtjt
d
ƒjddƒƒ‚q—|}ng}t}|rD||||jƒ\}}} }!x|D]l\}"}#}$|#dkrtjt
dƒ|"ƒ‚n|"dkrg}Pn
|j|#ƒ|p:|$d7k}qÑWnŸ|dk	r…t|ƒdkr…|djƒr…|djƒ}%nd}%tjj|%ƒ\}&}"|&jƒ}|j|jƒjƒt|||jƒƒ\} }!|jƒjdƒrt}n|r+t j!j"ƒs+tj#dƒ‚q+n|s:d}'nd}'|sOd}(n|r^d}(nd}(|dkr…t$j%j&|ƒ}ntjj'ddƒ})|d|d|j(d |)d!|d"t)ƒd#|	d$|	dkd%|ƒ}*|oñ|j*j+j,}+t|ƒdkp|p|'p|+},i}-|r1||-d<n|rD||-d&<n|rW||-d'<n|rj||-d(<n|r}||-d)<nt|ƒdkr˜d}n|d*|d+|d,| d-|!d.|d/|
d0|'d1|(d2|,d3|d4|-d5|d6|ƒ
}.|||.ƒj-|*ƒdS(8Ni(tLoggertmake_log_request_dictt_get_info_for_log_filesR¦R(tdeprecated_command_optionRÃs--include-mergesRÄs--include-mergedRÅs2.5tcommands"{0} and {1} are mutually exclusiveis8--exclude-common-ancestry requires -r with two revisionss--levelsis
--revisions--changes2Path unknown at end or start of revision range: %sRƒRrstree-referenceR;tvalidate_signatures_in_logtfulltpartialR—R¹R„R†t
to_exact_filet
show_timezonetdelta_formatR«tshow_advicetauthor_list_handlerRt	committertauthortbugst	directiontspecific_fileidststart_revisiontend_revisionR®tmessage_searcht
delta_typet	diff_typet_match_using_deltastexclude_common_ancestryR±t	signaturetomit_merges(s	directorystree-reference(.t
bzrlib.logR´RµR¶Rtdeprecated_passedRÌRÍRÎRËRRRcRZR®R!RbtRangeInChangeOptionRöRt
get_branchRRRQRR¬R°t_get_revision_rangeRCtget_config_stackR¿RGtgpgtGPGStrategytverify_signatures_availabletGpgmeNotInstalledR•tlog_formatter_registrytget_defaulttmake_output_streamR‹RR«R%t
supports_chkstshow(/RŒR[R§RvR„R¦RjRut
log_formatR«RR®t	show_difftinclude_mergedR¨RÌR°R±t
match_messagetmatch_committertmatch_authort
match_bugsRÎtinclude_mergesR´RµR¶RÄRQt
filter_by_dirR²tfile_info_listtrev1trev2R]RNRER5R@RÉRÊtunencoded_outputtlftpartial_historytmatch_using_deltast
match_dicttrqst((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¢
sÒ	
												

"						




	(s
bzrlib.logRªN(R‘R’R“R”R˜RRR)toptionR	RR£RRGR¡RR•R—RRR!RtDEPRECATED_PARAMETERR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¤¼	s¬š																	c	C@s?|dkrd}d}nt|ƒdkrG|dj|ƒ}}nît|ƒdkr|d}|d}|jƒ|jƒkr¡tjtdƒ|ƒ‚n|jdkrÅt|ddƒ}n|j|ƒ}|jdkr
|j	ƒ\}}t|||ƒ}q5|j|ƒ}ntjtdƒ|ƒ‚||fS(sÜTake the input of a revision option and turn it into a revision range.

    It returns RevisionInfo objects which can be used to obtain the rev_id's
    of the desired revisions. It does some user input validations.
    iiis:bzr %s doesn't accept two revisions in different branches.s*bzr %s --revision takes one or two values.N(
RRbR¯RÒRRcRZtspectRevisionInfotlast_revision_info(	trevisionspec_listR-RdRèRét
start_spectend_spect
last_revnotlast_revision_id((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÓPs,	

	
	cC@sVd}d}|ddk	r,|dj}n|ddk	rL|dj}n||fS(Nii(RRµ(trevision_rangetrev_id1trev_id2((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_revision_range_to_revid_rangewstlongcC@s7|}|rd}n|r$d}n|r3d}n|S(NRþRwtline((RþRwRÿRLRÞ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytget_log_format€s			tcmd_touching_revisionscB@s,eZdZeZdgZed„ƒZRS(sqReturn revision-ids which affected a particular file.

    A more user-friendly interface is "bzr log FILE".
    R_c
C@stj|ƒ\}}|j|ƒ}|j}|j|jƒjƒtj||ƒ}x1|D])\}}}	|j	j
d||	fƒq\WdS(Ns%6d %s
(RPRQR4R-RöR¬R°R•tfind_touching_revisionsR‹R£(
RŒR_R\R]RNR²t
touching_revsRR±twhat((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR”s	(R‘R’R“RGR¶R”RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR‹s	tcmd_lscB@séeZdZddgZdgZddedddd	d
ƒedd	dƒed
ddd	dƒedd	dddƒedddd	dƒedddd	ddeƒdddgZede
e
e
e
e
e
e
de
ddd„ƒZRS(sList files in a tree.
    Rþtcatspath?RvRjRèRyRéRxsRecurse into subdirectories.s	from-roots/Print paths relative to the root of the branch.tunknowntusPrint unknown files.R{sPrint versioned files.R|R.R
sPrint ignored files.RER	s<List entries of a particular kind: file, directory, symlink.RRŽsshow-idsRrc
 C@sÑ|	r*|	dkr*tjtdƒƒ‚n|rN|rNtjtdƒƒ‚n|p]|p]|}
i|d6|d6|d6}|dkr‘d	}n$|r¯tjtd
ƒƒ‚n|}t||ƒ\}}}d}|rï|r|d}qn)|d	kr|jdƒr|d}n|dk	s0|dkrHtd|d
|ƒ}nt}t|t	ƒr|j
ƒr|jjƒ}|rt
}tj|ƒ}ttdƒ|ƒqn|j|jƒjƒx|jdtd|d|ƒD]ç\}}}}}|
r||rqân|	dk	r-||	kr-qân|r…y5|rQtj||ƒ}n|}tj||ƒWq…tjk
rqâq…Xn|r tj||ƒ}n|jƒ}||}tjjƒ|rd||f}|
rþ|dk	rþd||f}n|jj|dƒqâ|rw|jj|dƒ|
rg|dk	rT|jj|ƒn|jjdƒn|jjƒqâ|
rµ|dk	r’|}nd}|jjd||fƒqâ|jj|dƒqâWdS(NRFRrRGsinvalid kind specifieds$Cannot set both --verbose and --nulltIt?R|R;s(cannot specify both --from-root and PATHR,RDR-s'Ignoring files outside view. View is %stinclude_roottfrom_dirRès%-8s %ss%-50s %ss
RRƒs	%-50s %s
(sfiles	directoryssymlink(RRcRZRRstendswithRkR!RVRPRRRSRTRGRYRRöR¬R°t
list_filesRURjtcheck_path_in_viewRWtkind_characterRÌRÍt
clear_termR‹R£tflush( RŒRjRvRèt	from_rootRR{R.RŽRER„RºRrtallt	selectiontfs_pathR\R-R]RóR{R^R`tfptfctfkindR4RStfullpathtkindcht	outstringtmy_id((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¹s‚	
"


	N(R‘R’R“R˜R”RR0R•RRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRŸs4				tcmd_unknownscB@s8eZdZeZdgZdgZedd„ƒZRS(sList unknown files.
    RDRru.cC@sEx>tj|ƒdjƒD]#}|jjtj|ƒdƒqWdS(Nis
(RPRQtunknownsR‹R£RUR‘(RŒRrR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs (	R‘R’R“RGR¶R˜R•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs		t
cmd_ignorecB@sPeZdZdddgZdgZdedddƒgZddd	d
„ZRS(sð	Ignore specified files or patterns.

    See ``bzr help patterns`` for details on the syntax of patterns.

    If a .bzrignore file does not exist, the ignore command
    will create one and add the specified files or patterns to the newly
    created file. The ignore command will also automatically add the 
    .bzrignore file to be versioned. Creating a .bzrignore file without
    the use of the ignore command will require an explicit add command.

    To remove patterns from the ignore list, edit the .bzrignore file.
    After adding, editing or deleting that file either indirectly by
    using this command or directly by using an editor, be sure to commit
    it.
    
    Bazaar also supports a global ignore file ~/.bazaar/ignore. On Windows
    the global ignore file can be found in the application data directory as
    C:\Documents and Settings\<user>\Application Data\Bazaar\2.0\ignore.
    Global ignores are not touched by this command. The global ignore file
    can be edited directly using an editor.

    Patterns prefixed with '!' are exceptions to ignore patterns and take
    precedence over regular ignores.  Such exceptions are used to specify
    files that should be versioned which would otherwise be ignored.
    
    Patterns prefixed with '!!' act as regular ignore patterns, but have
    precedence over the '!' exception patterns.

    :Notes: 
        
    * Ignore patterns containing shell wildcards must be quoted from
      the shell on Unix.

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

    :Examples:
        Ignore the top level Makefile::

            bzr ignore ./Makefile

        Ignore .class files in all directories...::

            bzr ignore "*.class"

        ...but do not ignore "special.class"::

            bzr ignore "!special.class"

        Ignore files whose name begins with the "#" character::

            bzr ignore "RE:^#"

        Ignore .o files under the lib directory::

            bzr ignore "lib/**/*.o"

        Ignore .o files under the lib directory::

            bzr ignore "RE:lib/.*\.o"

        Ignore everything but the "debian" toplevel directory::

            bzr ignore "RE:(?!debian/).*"
        
        Ignore everything except the "local" toplevel directory,
        but always ignore autosave files ending in ~, even under local/::
        
            bzr ignore "*"
            bzr ignore "!./local"
            bzr ignore "!!*~"
    RþR.tpatternss
name_pattern*Rrs
default-rulesRxs/Display the default ignore rules that bzr uses.u.cC@sSddlm}|dk	rHx%|jD]}|jjd|ƒq&WdS|sftjtdƒƒ‚ng|D]}t	j
|ƒ^qm}d}d}x;|D]3}t	jj|ƒs›|d7}|d|7}q›q›W|rt
dd	|ƒ|}	tjj|	ƒtjdƒ‚nxX|D]P}
|
dd
ksOt|
ƒdkr|
ddkrtjtdƒƒ‚qqWtj|ƒ\}}|j||ƒt	j|ƒ}
g}|j|jƒjƒxV|jƒD]H}|d
}|dk	rÈ|d}|
j|ƒr|j|ƒqqÈqÈWt|ƒdkrO|jjtdƒdj|ƒfƒndS(Ni(tignoress%s
s=ignore requires at least one NAME_PATTERN or --default-rules.Rƒis
  %ss Invalid ignore pattern found. %ss!Invalid ignore patterns found. %sR,Rzs+NAME_PATTERN should not be an absolute pathis§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.
s
(R)R"Rt
USER_DEFAULTSR‹R£RRcRZtglobbingtnormalize_patterntGlobstertis_pattern_validRßRÌRÍt
show_errortInvalidPatternRbRPRQttree_ignores_add_patternsRöR¬R°RR±RR4(RŒtname_pattern_listt
default_rulesRrR"tpatternR3tbad_patternstbad_patterns_countR³tname_patternR\R]R.tmatchesRSR“R_((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRssP



"	

N(	R‘R’R“R˜R”RR•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR "sH		tcmd_ignoredcB@s;eZdZdZddgZdgZedd„ƒZRS(sá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::

        bzr ls --ignored
    RRRDRru.c	C@sŽtj|ƒd}|j|jƒjƒx^|jƒD]P\}}}}}|dkr]q6n|j|ƒ}|jjd||fƒq6WdS(NiR	s	%-50s %s
(	RPRQRöR¬R°RR‘R‹R£(	RŒRrR\Rºt
file_classRERNRStpat((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR²s"(R‘R’R“R—R˜R•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR2£s		tcmd_lookup_revisioncB@s8eZdZeZdgZdgZedd„ƒZRS(saLookup the revision-id from a revision-number

    :Examples:
        bzr lookup-revision 33
    RRru.cC@styt|ƒ}Wn*tk
r<tjtdƒ|ƒ‚nXtj|ƒdjj|ƒ}|j	j
d|ƒdS(Nsnot a valid revision-number: %ris%s
(R‰RŸRRcRZRPRQR-t
get_rev_idR‹R£(RŒRRrR¥((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÈs
(	R‘R’R“RGR¶R”R•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR5¾s		t
cmd_exportc
B@s¤eZdZdZddgZdeddddeƒd	ed
ddƒeddedd
ƒedddƒedddƒgZdddde
e
e
dd„ZRS(sÀExport current or past revision to a destination directory or archive.

    If no revision is specified this exports the last committed revision.

    Format may be an "exporter" name, such as tar, tgz, tbz2.  If none is
    given, try to find the format with the extension. If no extension
    is found exports to a directory (equivalent to --format=dir).

    If root is supplied, it will be used as the root directory inside
    container formats (tar, zip, etc). If it is not supplied it will default
    to the exported filename. The root option has no effect for 'dir' format.

    If branch is omitted then the branch containing the current working
    directory will be used.

    Note: Export of tree with non-ASCII filenames to zip is not supported.

      =================       =========================
      Supported formats       Autodetected by extension
      =================       =========================
         dir                         (none)
         tar                          .tar
         tbz2                    .tar.bz2, .tbz2
         tgz                      .tar.gz, .tgz
         zip                          .zip
      =================       =========================
    R¹Rqsbranch_or_subdir?RrR®RxsType of file to export to.RRjtfilterss4Apply content filters to export the convenient form.R)s4Name of the root directory inside the exported file.sper-file-timestampssTSet modification time of files to that of the last revision in which it was changed.tuncommittedsGExport the working tree contents rather than that of the last revision.u.c

C@sddlm}
|dkr%|	}ntjj|ƒ\}}}
|dk	re|j|jƒjƒn|r˜|dkrt	j
tdƒƒ‚n|}ntd|d|d|ƒ}y&|
|||||
d|d|ƒWn2t	j
k
r
}t	j
td	ƒ|jƒ‚nXdS(
Ni(texports%--uncommitted requires a working treeR:R-R\tfilteredtper_file_timestampssUnsupported export format: %s(t
bzrlib.exportR:RRRRqRöR¬R°RRcRZRktNoSuchExportFormatR®(RŒRqtbranch_or_subdirRjR®R)R8R<R9RrR:R\R²tsubdirtexport_treeRý((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR
s&			N(R‘R’R“R·R”RR0RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR7Ós&					tcmd_catcB@steZdZdgZdedddƒedddƒdgZd	gZd
Zed
e
e
d
d„ƒZd„ZRS(sèWrite the contents of a file as of a given revision to standard output.

    If no revision is nominated, the last revision is used.

    Note: Take care to redirect standard output when using this command on a
    binary file.
    RDRrsname-from-revisionRxsThe path name in the old tree.R8s6Apply content filters to display the convenience form.RjR_R¹c	C@sƒ|dk	r6t|ƒdkr6tjtdƒƒ‚nt||ƒ\}}}|j|jƒjƒ|j	|||||||ƒS(Nis7bzr cat --revision takes exactly one revision specifier(
RRbRRcRZRsRöR¬R°R[(	RŒR_Rjtname_from_revisionR8RrR\R-R]((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR1
scC@sp|dkr|jƒ}ntd|d|ƒ}|j|jƒjƒ|j|ƒ}	|rš|	dkr‘tjt	dƒj
||jƒƒƒ‚q	|	}
no|j|ƒ}|dk	rÍ|j|ƒrÍ|}
n<|	dk	râ|	}
n'tjt	dƒj
||jƒƒƒ‚|rCddl
m}|||jƒ}
|
j|
ƒ}n|j|
ƒ}|jƒ|jj|ƒdS(NRR-s${0!r} is not present in revision {1}i(tContentFilterTree(RRgRkRöR¬R°R4RRcRZR®tget_revision_idR‹tbzrlib.filter_treeRDt_content_filter_stackt
get_file_textRR‹R£(RŒR\R²R]R_RjRCR;Ritold_file_idtactual_file_idtcur_file_idRDtfilter_treetcontent((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR[=
s6							
N(
R‘R’R“R˜RR•R”R—RRR!RR[(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRB
s			
tcmd_local_time_offsetcB@s#eZdZeZed„ƒZRS(s2Show the offset in seconds from GMT to local time.cC@s|jjdtjƒƒdS(Ns%s
(R‹R£RUtlocal_time_offset(RŒ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRj
s(R‘R’R“RGR¶RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRNg
st
cmd_commitcB@s^eZdZddddgZdgZeddedd	d
dƒeddedd
d
dƒdedd
dƒeddeddddd
dƒedd
dƒedded
dƒedded
dƒedded
dƒedd
d ƒed!dd"d
d#ƒed$d
d%ƒgZ	d&d'gZ
d(„Zd*d*e
d*e
e
e
d*d*e
d*d*e
d)„
ZRS(+s5	Commit changes into a new revision.

    An explanatory message needs to be given for each commit. This is
    often done by using the --message option (getting the message from the
    command line) or by using the --file option (getting the message from
    a file). If neither of these options is given, an editor is opened for
    the user to enter the message. To see the changed files in the
    boilerplate text loaded into the editor, use the --show-diff option.

    By default, the entire tree is committed and the person doing the
    commit is assumed to be the author. These defaults can be overridden
    as explained below.

    :Selective commits:

      If selected files are specified, only changes to those files are
      committed.  If a directory is specified then the directory and
      everything within it is committed.
  
      When excludes are given, they take precedence over selected files.
      For example, to commit only changes within foo, but not changes
      within foo/bar::
  
        bzr commit foo -x foo/bar
  
      A selective commit after a merge is not yet supported.

    :Custom authors:

      If the author of the change is not the same person as the committer,
      you can specify the author's name using the --author option. The
      name should be in the same format as a committer-id, e.g.
      "John Doe <jdoe@example.com>". If there is more than one author of
      the change you can specify the option multiple times, once for each
      author.
  
    :Checks:

      A common mistake is to forget to add a new file or directory before
      running the commit command. The --strict option checks for unknown
      files and aborts the commit if any are found. More advanced pre-commit
      checks can be implemented by defining hooks. See ``bzr help hooks``
      for details.

    :Things to note:

      If you accidentially commit the wrong changes or make a spelling
      mistake in the commit message say, you can use the uncommit command
      to undo it. See ``bzr help uncommit`` for details.

      Hooks can also be configured to run after a commit. This allows you
      to trigger updates to external systems like bug trackers. The --fixes
      option can be used to record the association between a revision and
      one or more bugs. See ``bzr help bugs`` for details.
    R RÃthookstuncommits	selected*texcludeRRytxRxs-Do not consider changes made to a given path.RR²s Description of the new revision.Rvt	unchangeds#Commit even if nothing has changed.RFRrR¬tmsgfiles#Take commit message from this file.Ršs@Refuse to commit if there are unknown files in the working tree.scommit-timesVManually set a commit time using commit date format, e.g. '2009-10-10 08:00:00 +0100'.tfixessAMark a bug as being fixed by this revision (see "bzr help bugs").RÂs<Set the author's name, if it's different from the committer.R~s€Perform a local commit in a bound branch.  Local commits are not pushed to the master branch until a normal commit is performed.s	show-diffR3s_When no message is supplied, show the diff along with the status summary in the message editor.tlossysjWhen committing to a foreign version control system do not push data that can not be natively represented.tcitcheckinc
c@sZd}xM|D]E}|jdƒ}t|ƒdkr™|dkr^|jƒ}|jdƒ}n|dkr†tjtdƒ|ƒ‚n|}|d}n:t|ƒdkrÇtjtdƒ|ƒ‚n|\}}ytj	|||ƒVWq
tj
k
rtjtdƒ|ƒ‚q
tjk
rQ}	tjtd	ƒt|	ƒfƒ‚q
Xq
WdS(
NRzit
bugtrackersÄNo tracker specified for bug %s. Use the form 'tracker:id' or specify a default bug tracker using the `bugtracker` option.
See "bzr help bugs" for more information on this feature. Commit refused.iis~Invalid bug %s. Must be in the form of 'tracker:id'. See "bzr help bugs" for more information on this feature.
Commit refused.s$Unrecognized bug %s. Commit refused.s%s
Commit refused.(
RR¼RbRÔR¿RRcRZR[tget_bug_urltUnknownBugTrackerAbbreviationtMalformedBugIdentifierR(
RŒRWR-tdefault_bugtrackert	fixed_bugttokenst
branch_configttagtbug_idRý((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_iter_bug_fix_urlsÔ
s6
	

	
		c@s3ddlm}m}m}ddlm‰m‰m‰m‰d}}|dk	r¥yt
j|ƒ\}}Wq¥tk
r¡}t
jtdt|ƒƒƒ‚q¥Xni}tjˆƒ\‰‰ˆdgkrØg‰n|dkríg}ntj|j|ˆjƒƒ}|r||d<n|rCˆjjƒrCt
jƒ‚nˆdk	rúytjˆƒ}Wntk
r{t}nX|r¦diˆd6}tjj|ƒnd	ˆkrÙˆj d
dƒ‰ˆj d	dƒ‰nˆrút
jtdƒƒ‚qún‡‡‡‡‡‡‡‡‡f	d
†}ˆs0d‰nyeˆj!d|dˆd|d|d|ddd|d|d|	d|d|dˆj"|ƒd|
ƒ
Wn—|k
r½t
jtdƒƒ‚nr|k
rât
jtdƒƒ‚nM|k
rt
jtdƒƒ‚n(t
j#k
r.}tdƒ|_$‚nXdS(Ni(tPointlessCommittConflictsInTreetStrictCommitFailed(tedit_commit_message_encodedt generate_commit_message_templatet$make_commit_message_template_encodedtset_commit_messagesCould not parse --commit-time: RƒRÃsfThe commit message is a file name: "%(f)s".
(use --file "%(f)s" to take commit message from that file)Rs
s
s
s)please specify either --message or --filec@sýˆrBtˆƒ}z|jƒjtjƒƒ}Wd|jƒXn·ˆdk	rWˆ}n¢ˆˆˆdˆdtjƒƒ}ˆ|ƒ}|dkr±ˆ|ƒ}ˆ|d|ƒ}n|dkrÕtjt	dƒƒ‚n|dkrùtjt	dƒƒ‚n|S(sCallback to get commit messageNR€toutput_encodingt
start_messages?please specify a commit message with either --message or --fileRƒs‹Empty commit message specified. Please specify a commit message with either --message or --file or leave a blank message with --message "".(
R treadR¤RUtget_user_encodingtcloseRRRcRZ(t
commit_objRt
my_messagettextRn(	RiRFRjRkRt
selected_listRlRßR\(s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytget_message7s(		tmessage_callbackR…tallow_pointlessRšR~treporterRvtrevpropsR¨t	timestampR§RSRXsqNo changes to commit. Please 'bzr add' the files you want to commit, or use --unchanged to force an empty commit.s`Conflicts detected in working tree.  Use "bzr conflicts" to list, "bzr resolve FILE" to resolve.sCCommit refused because there are unknown files in the working tree.s~
To commit to master branch, run update and then commit.
You can also pass --local to commit to continue working disconnected.(%t
bzrlib.errorsRfRgRhtbzrlib.msgeditorRiRjRkRlRR{tparse_patch_dateRŸRRcRZRRPRŠR[tencode_fixes_bug_urlsReR-RR†RURgtUnicodeErrorR!RÌRÍtshow_warningRtcommittsafe_relpath_filestBoundBranchOutOfDatet
extra_help(RŒRRFRvRuRURšR~RWRÂRßRStcommit_timeRXRfRgRhtcommit_stamptoffsetRýt
propertiestbug_propertytfile_existstwarning_msgRv((	RiRFRjRkRRuRlRßR\s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR÷
sr"
			

	'&	


N(R‘R’R“R˜R”RRRR0R•R–ReRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRPp
sF7						#t	cmd_checkcB@sneZdZdgZdgZdedddƒedddƒed	dd
ƒgZdeeeed„Z	RS(
s	Validate working tree structure, branch consistency and repository history.

    This command checks various invariants about branch and repository storage
    to detect data corruption or bzr bugs.

    The working tree and branch checks will only give output if a problem is
    detected. The output fields of the repository check are:

    revisions
        This is just the number of revisions checked.  It doesn't
        indicate a problem.

    versionedfiles
        This is just the number of versionedfiles checked.  It
        doesn't indicate a problem.

    unreferenced ancestors
        Texts that are ancestors of other texts, but
        are not properly referenced by the revision ancestry.  This is a
        subtle problem that Bazaar can work around.

    unique file texts
        This is the total number of unique file contents
        seen in the checked revisions.  It does not indicate a problem.

    repeated file texts
        This is the total number of repeated texts seen
        in the checked revisions.  Texts can be repeated when their file
        entries are modified, but the file contents are not.  It does not
        indicate a problem.

    If no restrictions are specified, all Bazaar data that is found at the given
    location will be checked.

    :Examples:

        Check the tree and branch at 'foo'::

            bzr check --tree --branch foo

        Check only the repository at 'bar'::

            bzr check --repo bar

        Check everything at 'baz'::

            bzr check baz
    R9spath?RvR-Rxs2Check the branch related to the current directory.RNs6Check the repository related to the current directory.R\s8Check the working tree related to the current directory.c	C@snddlm}|dkr%d}n|rK|rK|rKt}}}n|||d|d|d|ƒdS(Ni(t
check_dwimR;t	do_branchtdo_repotdo_tree(tbzrlib.checkRŽRRG(RŒRºRvR-RNR\RŽ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR·s	N(
R‘R’R“R˜R”RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR{s0		tcmd_upgradecB@s‰eZdZdddgZdgZeddddddd„d
eddƒedddƒedddƒgZdde
e
d„ZRS(sAUpgrade a repository, branch or working tree to a newer format.

    When the default format has changed after a major new release of
    Bazaar, you may be informed during certain operations that you
    should upgrade. Upgrading to a newer format may improve performance
    or make new features available. It may however limit interoperability
    with older repositories or with older versions of Bazaar.

    If you wish to upgrade to a particular format rather than the
    current default, that can be specified using the --format option.
    As a consequence, you can use the upgrade command this way to
    "downgrade" to an earlier format, though some conversions are
    a one way process (e.g. changing from the 1.x default to the
    2.x default) so downgrading is not always possible.

    A backup.bzr.~#~ directory is created at the start of the conversion
    process (where # is a number). By default, this is left there on
    completion. If the conversion fails, delete the new .bzr directory
    and rename this one back in its place. Use the --clean option to ask
    for the backup.bzr directory to be removed on successful conversion.
    Alternatively, you can delete it by hand if everything looks good
    afterwards.

    If the location given is a shared repository, dependent branches
    are also converted provided the repository converts successfully.
    If the conversion of a branch fails, remaining branches are still
    tried.

    For more information on upgrades, see the Bazaar Upgrade Guide,
    http://doc.bazaar.canonical.com/latest/en/upgrade-guide/.
    R8R9tformatssurl?R®RxsBUpgrade to a specific format.  See "bzr help formats" for details.RGsbzrlib.controldirRHRIcC@stjj|ƒS(N(RRHRJ(RC((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRKésR!R s
Branch formattcleans.Remove the backup.bzr directory if successful.sdry-runs8Show what would be done, but don't actually do anything.R;cC@s[ddlm}|||d|d|ƒ}|rWt|ƒdkrP|d‚qWdSndS(Ni(tupgradetclean_upR'ii(tbzrlib.upgradeR–Rb(RŒRcR®R•R'R–t
exceptions((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRñs
(sbzrlib.controldirsformat_registryN(R‘R’R“R˜R”RRGRR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR“Ás					t
cmd_whoamicB@s_eZdZdedddƒedddƒgZdgZdZeeed
d
d	„ƒZ
RS(sÑShow or set bzr user id.

    :Examples:
        Show the email of the current user::

            bzr whoami --email

        Set the current user::

            bzr whoami "Frank Chu <fchu@example.com>"
    RrtemailRxsDisplay email address only.R-s8Set identity for the current branch instead of globally.sname?Rc	C@s”|dkr½|dkr[ytjdƒdjƒ}Wqptjk
rWtjƒ}qpXntj|ƒjƒ}|j	dƒ}|r¥|j
jtj|ƒdƒn|j
j|dƒdS|rÛtj
tdƒƒ‚nytj|ƒWn#tjk
r}td|ƒnX|rt|dkr@tjdƒdjƒ}q€tj|ƒ}|j|jƒjƒ|jƒ}ntjƒ}|jd|ƒdS(Nu.iR›s
s5--email can only be used to display existing identitysV"%s" does not seem to contain an email address.  This is allowed, but not recommended.(RR9RQRÔRRt_mod_configtGlobalStackR R¿R‹R£textract_email_addressRcRZtNoEmailInUsernameRRöR…R°R@(	RŒR›R-RCRrRtidentityRýR²((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs8N(R‘R’R“RR•R”R—RR!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRšüs			tcmd_nickcB@sGeZdZdgZdgZdgZddd„Zed„ƒZ	RS(sCPrint or set the branch nickname.

    If unset, the colocated branch name is used for colocated branches, and
    the branch directory name is used for other branches.  To print the
    current nickname, execute with no argument.

    Bound branches use the nickname of its master branch unless it is set
    locally.
    Rs	nickname?Rru.cC@s<tj|ƒd}|dkr/|j|ƒn	||_dS(Ni(R9RQRtprintmetnick(RŒtnicknameRrR-((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRKscC@s|jjd|jƒdS(Ns%s
(R‹R£R£(RŒR-((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¢RsN(
R‘R’R“R˜R”R•RRRR¢(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¡=s				t	cmd_aliascB@skeZdZdgZedddƒgZd
ed„Zd„Z	e
d„ƒZe
d„ƒZd	„Z
RS(sQSet/unset and display aliases.

    :Examples:
        Show the current aliases::

            bzr alias

        Show the alias specified for 'll'::

            bzr alias ll

        Set an alias for 'll'::

            bzr alias ll="log --line -r-10..-1"

        To remove an alias for 'll'::

            bzr alias --remove ll

    sname?RRxsRemove the alias.cC@sz|r|j|ƒn`|dkr/|jƒnG|jdƒ}|dkrZ|j|ƒn|j|| ||dƒdS(Nt=iÿÿÿÿi(tremove_aliasRt
print_aliasestfindtprint_aliast	set_alias(RŒRCRt	equal_pos((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRqs
cC@sA|dkr$tjtdƒƒ‚ntjƒ}|j|ƒdS(Ns.bzr alias --remove expects an alias to remove.(RRRcRZRœtGlobalConfigtunset_alias(RŒt
alias_nameR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR§}s
	cC@sStjƒjƒ}x:t|jƒƒD]&\}}|jjd||fƒq%WdS(s:Print out the defined aliases in a similar format to bash.sbzr alias %s="%s"
N(RœRtget_aliasesR$RBR‹R£(RŒR–tkeytvalue((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¨†scC@sfddlm}||ƒ}|dkr?|jjd|ƒn#|jjd|dj|ƒfƒdS(Ni(t	get_aliassbzr alias: %s: not found
sbzr alias %s="%s"
Rë(tbzrlib.commandsR³RR‹R£R4(RŒR¯R³talias((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRªs	cC@s tjƒ}|j||ƒdS(s$Save the alias in the global config.N(RœRR«(RŒR¯t
alias_commandR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR«—sN(R‘R’R“R”RR•RR!RR§RR¨RªR«(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¥Ws			
tcmd_selftestcB@sèeZdZd„ZeZdgZdedddddƒed	dd
deƒeddd
deƒedddƒedddƒedddddƒedddƒeddddd<de	ƒedde
dd dd!ƒed"de
dd#dd$dd%ƒed&dd'ƒed(dd)ƒed*de
dd+dd,ƒed-de
dd.dd/ƒed0de
dd1d2d3dd4dd5ƒed6dd7ƒgZd8Z
d9„Zd=e	e	d=d=d=e	e	d=d=e	d=d=d=e	d=e	e	d:„Zd;„ZRS(>sRun internal test suite.

    If arguments are given, they are regular expressions that say which tests
    should run.  Tests matching any expression are run, and other tests are
    not run.

    Alternatively if --first is given, matching tests are run first and then
    all other tests are run.  This is useful if you have been working in a
    particular area, but want to make sure nothing else was broken.

    If --exclude is given, tests that match that regular expression are
    excluded, regardless of whether they match --first or not.

    To help catch accidential dependencies between tests, the --randomize
    option is useful. In most cases, the argument used is the word 'now'.
    Note that the seed used for the random number generator is displayed
    when this option is used. The seed can be explicitly passed as the
    argument to this option if required. This enables reproduction of the
    actual ordering used if and when an order sensitive problem is encountered.

    If --list-only is given, the tests that would be run are listed. This is
    useful when combined with --first, --exclude and/or --randomize to
    understand their impact. The test harness reports "Listed nn tests in ..."
    instead of "Ran nn tests in ..." when list mode is enabled.

    If the global option '--no-plugins' is given, plugins are not loaded
    before running the selftests.  This has two effects: features provided or
    modified by plugins will not be tested, and tests provided by plugins will
    not be run.

    Tests that need working space on disk use a common temporary directory,
    typically inside $TMPDIR or /tmp.

    If you set BZR_TEST_PDB=1 when running selftest, failing tests will drop
    into a pdb postmortem session.

    The --coverage=DIRNAME global option produces a report with covered code
    indicated.

    :Examples:
        Run only tests relating to 'ignore'::

            bzr selftest ignore

        Disable plugins and list tests as they're run::

            bzr --no-plugins selftest -v
    cC@s†|dkr#ddlm}|jS|dkrFddlm}tjS|dkriddlm}|jSd|}tj|ƒ‚dS(	s'Parse and return a transport specifier.tsftpi(t	stub_sftptmemory(ttest_servertfakenfss6No known transport type %s. Supported types are: sftp
N(	tbzrlib.testsR¹tSFTPAbsoluteServerR»RºtMemoryServert
FakeNFSServerRRc(t
typestringR¹R»R³((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pytget_transport_typeÐss
testspecs*RvtoneRxsStop when one test fails.RyRyR½s?Use a different transport by default throughout the test suite.Rt	benchmarks)Run the benchmarks rather than selftests.R¶slsprof-timeds8Generate lsprof output for benchmarked sections of code.slsprof-testss%Generate lsprof output for each test.tfirsts-Run all tests, but run specified tests first.Rs	list-onlys'List the tests instead of running them.tparallelsRun the test suite in parallel.RGsbzrlib.teststparallel_registryR!t	randomizeR¬tSEEDsPRandomize the order of tests using the given seed or "now" for the current time.RStPATTERNRTs1Exclude tests that match this regular expression.tsubunits!Output test progress via subunit.Ršs/Fail on missing dependencies or known failures.s	load-listtTESTLISTFILEs%Load a test id list from a text file.t	debugflagtEsTurn on a selftest debug flag.s
starting-withtTESTIDt
param_namet
starting_withR¢s)Load only the tests starting with TESTID.tsyncsGBy default we disable fsync and fdatasync while running the test suite.RcC@stj|ƒi|_dS(N(Rt__init__tadditional_selftest_args(RŒ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÓs
cC@sItjƒyddlm}Wn tk
r@tjdƒ‚nX|dk	r_dj|ƒ}nd}|r
yddl	m
}Wn&tk
r§tjtdƒƒ‚nX||jd<t
jd	kr
tt
jd
dƒdk	r
ddl}|jt
jjƒtjƒq
n|r2|jjdgƒj|ƒn|rPtjtdƒƒ‚nd}|
sed}nd
dj|
ƒd}|s|jƒni|d6|d6|d6|d6|d6|d6|d6|d6|d6|	d6|d6|d6|d6|
d6|d6}|j|jƒtjdtƒ}z|j|}Wd|ƒXt|ƒS(Ni(ttestssVtests not available. Install the python-bzrlib.tests package to run the bzr testsuite.t|s.*(tSubUnitBzrRunnersFsubunit not available. subunit needs to be installed to use --subunit.trunner_classtwin32tfilenotsuite_decoratorssI--benchmark is no longer supported from bzr 2.2; use bzr-usertest insteadt(t)RvR-tstop_on_failureR½ttest_suite_factorytlsprof_timedtlsprof_teststmatching_tests_firstt	list_onlytrandom_seedtexclude_patternRšt	load_listtdebug_flagsRÑtoverride(Rtdisallow_proxyingR)RÕtImportErrorRRcRR4R½R×RZRÔRƒtplatformR˜R„tmsvcrttsetmodeRÚR8tO_BINARYt
setdefaultRt_disable_fsyncRzRtactivate_deprecation_warningsR!tselftestR‰(RŒttestspecs_listRvRÃR½RÄRàRÅRãRÈRSRšRæRÍRÑRËRÆRáRÒRÕR-R×RìRßRåtselftest_kwargstcleanupR£((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRsh



"			

		cC@sjttddƒ|_|jdk	r3d„t_nttddƒ|_|jdk	rfd„t_ndS(s1Change the 'os' functionality to not synchronize.tfsynccS@sdS(N(R(tfiledes((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRKrst	fdatasynccS@sdS(N(R(R÷((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRKusN(R˜R8Rt_orig_fsyncRöt_orig_fdatasyncRø(RŒ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRðns(sbzrlib.testsRÇN(R‘R’R“RÂRGR¶R”RRR!RRR•R—RÓRRRð(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR·sn0															Mtcmd_versioncB@s;eZdZdZedddƒgZeed„ƒZRS(sShow version of bzr.RRwRxsPrint just the version number.cC@sDddlm}|r0|jjtjdƒn|d|jƒdS(Ni(tshow_versions
R†(tbzrlib.versionRüR‹R£R)tversion_string(RŒRwRü((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR€s(	R‘R’R“R—RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRûxs
t	cmd_rockscB@s#eZdZeZed„ƒZRS(sStatement of optimism.cC@s|jjtdƒƒdS(NsIt sure does!
(R‹R£RZ(RŒ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRŽs(R‘R’R“RGR¶RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÿ‰stcmd_find_merge_basecB@s/eZdZddgZeZed„ƒZRS(s8Find and print a base revision for merging two branches.R-totherc
C@sËddlm}tj|ƒd}tj|ƒd}|j|jƒjƒ|j|jƒjƒ||jƒƒ}||jƒƒ}|jj	|jƒ}|j
||ƒ}	|jjt
dƒ|	ƒdS(Ni(Rsmerge base is revision %s
(tbzrlib.revisionRR9RQRöR¬R°RR«R=tfind_unique_lcaR‹R£RZ(
RŒR-RRtbranch1tbranch2tlast1tlast2RBtbase_rev_id((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRšs(R‘R’R“R”RGR¶RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR“st	cmd_mergecB@s7eZdZdZddddgZdgZdded	d
dƒdd
dedd
dƒedd
dƒedd
dƒedd
dƒedd
dƒedd
dddƒgZd'd'e
d'e
d'd'e
e
d'e
e
d„Zd„Zd„Z
d „Zd!„Zd"„Zd#„Zd$„Zd'd'd%„Zd&„ZRS((sBPerform a three-way merge.

    The source of the merge 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. If neither is specified, the default is the upstream branch
    or the branch most recently merged using --remember.  The source of the
    merge may also be specified in the form of a path to a file in another
    branch:  in this case, only the modifications to that file are merged into
    the current working tree.

    When merging from a branch, by default bzr will try to merge in all new
    work from the other branch, automatically determining an appropriate base
    revision.  If this fails, you may need to give an explicit base.

    To pick a different ending revision, pass "--revision OTHER".  bzr will
    try to merge in all new work up to and including revision OTHER.

    If you specify two values, "--revision BASE..OTHER", only revisions BASE
    through OTHER, excluding BASE but including OTHER, will be merged.  If this
    causes some revisions to be skipped, i.e. if the destination branch does
    not already contain revision BASE, such a merge is commonly referred to as
    a "cherrypick". Unlike a normal merge, Bazaar does not currently track
    cherrypicks. The changes look like a normal commit, and the history of the
    changes from the other branch is not stored in the commit.

    Revision numbers are always relative to the source branch.

    Merge will do its best to combine the changes in two branches, but there
    are some kinds of problems only a human can fix.  When it encounters those,
    it will mark a conflict.  A conflict means that you need to fix something,
    before you can commit.

    Use bzr resolve when you have fixed a problem.  See also bzr conflicts.

    If there is no default branch set, the first merge will set it (use
    --no-remember to avoid setting it). After that, you can omit the branch
    to use the default.  To change the default, use --remember. The value will
    only be saved if the remote location can be accessed.

    The results of the merge are placed into the destination working
    directory, where they can be reviewed (with bzr diff), tested, and then
    committed to record the result of the merge.

    merge refuses to run if there are any uncommitted changes, unless
    --force is given.  If --force is given, then the changes from the source 
    will be merged with the current working tree, including any uncommitted
    changes in the tree.  The --force option can also be used to create a
    merge revision which has more than two parents.

    If one would like to merge changes from the working tree of the other
    branch without merging any committed revisions, the --uncommitted option
    can be given.

    To select only some changes to merge, use "merge -i", which will prompt
    you to apply each diff hunk and file change, similar to "shelve".

    :Examples:
        To merge all new revisions from bzr.dev::

            bzr merge ../bzr.dev

        To merge changes up to and including revision 82 from bzr.dev::

            bzr merge -r 82 ../bzr.dev

        To merge the changes introduced by 82, without previous changes::

            bzr merge -r 81..82 ../bzr.dev

        To apply a merge directive contained in /tmp/merge::

            bzr merge /tmp/merge

        To create a merge revision with three parents from two branches
        feature1a and feature1b:

            bzr merge ../feature1a
            bzr merge ../feature1b --force
            bzr commit -m 'revision with three parents'
    R¹Rztremergesstatus-flagsR{s	location?RuRjRëRxs;Merge even if the destination tree has uncommitted changes.s
merge-typet	reprocessR|s	show-bases%Show base revision text in conflicts.R9sIApply uncommitted changes from a working copy, instead of branch changes.Rs¤If the destination is already completely merged into the source, pull from the source rather than merging.  When this happens, you do not need to commit the result.RrsKBranch to merge into, rather than the one containing the working directory.tpreviews-Instead of merging, show a diff of the merge.tinteractivesSelect changes interactively.RyR
c
C@s|dkrtj}n|
dkr-d}
ng}
d}t}d}tj|
ƒd}|jjƒdkr…tj	t
dƒƒ‚ny|j|jƒƒ}Wn tj
k
rÀ|jƒ}nX|sè|jƒrètj|ƒ‚qènt|ƒ}tjd|jd|ƒ}tjjƒ}|j|jƒ|j|jƒjƒ|dk	réytj|d|
ƒ}Wntjk
r…d}qéX|r¤tj	t
dƒƒ‚n|dk	rÈtj	t
d	ƒƒ‚ntjj ||dƒ\}}n|dkrO|rO|dk	r1t!|ƒdkr1tj	t
d
ƒƒ‚n|j"||dƒ}t#}n|dkr‚|j$|||||
dƒ\}}n||_%||_&||_'|j(|ƒ|j)|j*kr3|j*dk	r3|j+r|j,j-|j+dƒst.t
dƒt/|ƒƒtj0|gƒ‚qnt.t
dƒƒdS|	r®|r®|j+dk	rgtj	t
d
ƒƒ‚n|j)|jƒkr®|j1|j2t#|j*ƒ}|j3|j4ƒdSn|j5dkrÕtj	t
dƒƒ‚n|rè|j6|ƒS|rû|j7|ƒS|j8||||ƒSdS(Nu.tinapplicableis_Merging into empty branches not currently supported, https://bugs.launchpad.net/bzr/+bug/308562R‚RnRs:Cannot use --uncommitted with bundles or merge directives.s.Cannot use -r with merge directives or bundless9Cannot use --uncommitted and --revision at the same time.smerger: sNothing to do.sCannot pull individual filessAThis branch has no commits. (perhaps you would prefer 'bzr pull')(9Rt
_mod_mergetMerge3MergerRGRPRQR-RRRcRZt
revision_treeRR¡RgRìRíRpRRR‘RÌRÍtnested_progress_barRötfinishedR…R°R‡RˆR‰tMergertfrom_mergeableRbtget_merger_from_uncommittedR!t_get_merger_from_brancht
merge_typeRRƒtsanity_check_mergerRtother_rev_idtinteresting_filest
other_treethas_filenameRRtPathsDoNotExistRtother_branchR’R‹t
this_basist_do_previewt_do_interactivet	_do_merge(RŒR5RjRëRRƒRR|R9RRrRR
Rtmergert
allow_pendingR R\RgRnR¢tpbRšR£((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs–		

						
		
	

cC@s8|jƒ}|jƒ}|j|jƒ|jƒ}|S(N(tmake_mergertmake_preview_transformRötfinalizetget_preview_tree(RŒR$ttree_mergerttttresult_tree((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_get_preview}s
c
C@sWddlm}|j|ƒ}tjƒ}||j||jddddd|ƒdS(Ni(RwR}RƒR~R(RRwR.RUR‚t	this_treeR‹(RŒR$RwR-R((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR!„scC@sY||_|jƒ}|r(|jƒn|dkrAtdƒn|dkrQdSdSdS(Ntfaileds$Preview patch does not match changesii(R¢tdo_mergetset_pendingR(RŒR$R¢R%R tconflict_count((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR#Œs	

c
C@s‡ddlm}|j|ƒ}tjjjƒ}|j|j|dtd|j	ƒd|t
jƒƒ}z|jƒWd|j
ƒXdS(sÝPerform an interactive merge.

        This works by generating a preview tree of the merge, then using
        Shelver to selectively remove the differences between the working tree
        and the preview tree.
        i(tshelf_uitdestroyRytdiff_writerN(R)R4R.Rðtdiff_writer_registryR¿tShelverR/RGt
ApplyReporterRƒR„RR)(RŒR$R4R-twritertshelver((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR"˜scC@sÓ|jr:|jtjk	r:tjtdƒ|jƒ‚n|jdkrp|jr^t	|_qp|jj
|_n|jr¥|jj
r¥tjtdƒ|jƒ‚n|jrÏ|jrÏtjtdƒƒ‚ndS(Ns2Show-base is not supported for this merge type. %ss6Conflict reduction is not supported for merge type %s.s+Cannot do conflict reduction and show base.(RƒRRRRRcRZRRR!tsupports_reprocess(RŒR$((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRªs		cC@søddlm}|j|||dƒ\}}	|dk	rmt|ƒdkrm|j|||dƒ\}
}n|}
tj||ƒ\}}
|
|kr |}ntj|
|ƒ\}}d}d}|dk	r#t|ƒdkrø|dj|ƒ}nt|ƒdkr#|dj|ƒ}q#n|dkrGtj	|j
ƒƒ}n|	dk	r|sz|dkr|jjƒdkr|jj
|jƒn|||jdtƒtjj||||||ƒ}|
dkrèt}|
g|_nt}||fS(	sAProduce a merger from a location, assuming it refers to a branch.i(RÁiÿÿÿÿiit
ignore_masterRƒN(RÊRÁt_select_branch_locationRRbR9RQR¯RRRR-tget_submit_branchtset_submit_branchRRGRRtfrom_revision_idsR!R(RŒR\R5RjR|RR&RÁt	other_loct
user_locationtbase_locRµRt
other_pathR,R+tother_revision_idRŸR$R%((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR½sH				cC@sb|j||ƒd}tj|ƒ\}}tjj|||ƒ}|dkr^|g|_n|S(sðGet a merger for uncommitted changes.

        :param tree: The tree the merger should apply to.
        :param location: The location containing uncommitted changes.
        :param pb: The progress bar to use for showing progress.
        iRƒ(R>RPRQRRtfrom_uncommittedR(RŒR\R5R&RRER$((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRòscC@s‚|dk	rQ|dk	rQ||dk	rQ||jƒ}|dk	rQ||fSn|dkrr|j|dƒ}n|}||fS(sSelect a branch location, according to possible inputs.

        If provided, branches from ``revision`` are preferred.  (Both
        ``revision`` and ``index`` must be supplied.)

        Otherwise, the ``location`` parameter is used.  If it is None, then the
        ``submit`` or ``parent`` location is used, and a note is printed.

        :param tree: The working tree to select a branch for merging into
        :param location: The location entered by the user
        :param revision: The revision parameter to the command
        :param index: The index to use for the revision parameter.  Negative
            indices are permitted.
        :return: (selected_location, user_location).  The default location
            will be the user-entered location.
        sMerging fromN(RRÒt_get_remembered(RŒR\RCRjtindexR-R5((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR>s
cC@sŸ|jjƒ}d}|dkr9|jjƒ}d}ntd|ƒ|dkrjtjtdƒƒ‚ntj	|dƒ}t
tdƒj|||ƒƒ|S(slUse tree.branch's parent if none was supplied.

        Report if the remembered location was used.
        tsubmitR·s%ss#No location specified or rememberedsutf-8s{0} remembered {1} location {2}N(R-R?RRŠR
RRcRZR1R‹RR®(RŒR\tverb_stringtstored_locationtstored_location_typeRž((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRHs	

N(R‘R’R“R—R˜R”RRR•RR!RR.R!R#R"RRRR>RH(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR	«sFP				_						5	tcmd_remergecB@sGeZdZdgZddedddƒgZddeed„ZRS(	sSRedo a merge.

    Use this if you want to try a different merge technique while resolving
    conflicts.  Some merge techniques are better than others, and remerge
    lets you try different ones on different files.

    The options for remerge have the same meaning and defaults as the ones for
    merge.  The difference is that remerge can (only) be run when there is a
    pending merge, and it lets you specify particular files.

    :Examples:
        Re-do the merge of all conflicted files, and show the base text in
        conflict regions, in addition to the usual THIS and OTHER texts::

            bzr remerge --show-base

        Re-do the merge of "foobar", using the weave merge algorithm, with
        additional processing to reduce the size of conflict regions::

            bzr remerge --merge-type weave --reprocess foobar
    sfile*s
merge-typeRs	show-baseRxs%Show base revision text in conflicts.cC@s¯ddlm}|dkr(tj}ntj|ƒ\}}|j|jƒj	ƒ|j
ƒ}t|ƒdkr‰tj
tdƒƒ‚n|jj}d}	g}
|jƒ}|dk	rttƒ}	x–|D]Ž}|j|ƒ}
|
dkrütj|ƒ‚n|	j|
ƒ|j|
ƒdkr$qÉnx0|jj|
ƒD]\}}|	j|jƒq7WqÉW|j||ƒd}
n1d	}g|D]}|j|kr|j^q}tj||jƒ|	ƒ|jt |
ƒƒ|dk	ræ|}nx<|D]4}y||j!|ƒƒWqítj"k
r qíXqíW|j#|d ƒzPtj$j%d||dƒ}|	|_&||_'||_(||_)|j*ƒ}Wd|j#|ƒX|dkr§dSdSdS(
Ni(trestoreisRSorry, remerge only works after normal merges.  Not cherrypicking or multi-merges.Rrs
text conflictscontents conflicti(s
text conflictscontents conflict(+tbzrlib.conflictsRORRRRPRŠRöR…R°RRbRRcRZR-R«RR@R4R/R REtroot_inventorytiter_entriesRNtselect_conflictsRÁRºttransform_treeRgt
set_conflictstConflictListRXt
NotConflictedtset_parent_idsRRAtinteresting_idsRRƒRR1(RŒR[RRƒRROR\R2R«RYt
new_conflictsRR_RNRCRŒtallowed_conflictsRt
restore_filesR$((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRNs`	


	
				N(	R‘R’R“R”RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRN0s			t
cmd_revertcB@sneZdZddddgZdeddƒedd	ƒgZd
gZd
ed
d
d„Z	e
d„ƒZRS(sŠ    Set files in the working tree back to the contents of a previous revision.

    Giving a list of files will revert only those files.  Otherwise, all files
    will be reverted.  If the revision is not specified with '--revision', the
    working tree basis revision is used. A revert operation affects only the
    working tree, not any revision history like the branch and repository or
    the working tree basis revision.

    To remove only some changes, without reverting to a prior version, use
    merge instead.  For example, "merge . -r -2..-3" (don't forget the ".")
    will remove the changes introduced by the second last commit (-2), without
    affecting the changes introduced by the last commit (-1).  To remove
    certain changes on a hunk-by-hunk basis, see the shelve command.
    To update the branch to a specific revision or the latest revision and
    update the working tree accordingly while preserving local changes, see the
    update command.

    Uncommitted changes to files that are reverted will be discarded.
    Howver, by default, any files that have been manually changed will be
    backed up first.  (Files changed only by merge are not backed up.)  Backup
    files have '.~#~' appended to their name, where # is a number.

    When you provide files, you can use their current pathname or the pathname
    from the target revision.  So you can use revert to "undelete" a file by
    name.  If you name a directory, all the contents of that directory will be
    reverted.

    If you have newly added files since the target revision, they will be
    removed.  If the files to be removed have been changed, backups will be
    created as above.  Directories containing unknown files will not be
    deleted.

    The working tree contains a list of revisions that have been merged but
    not yet committed. These revisions will be included as additional parents
    of the next commit.  Normally, using revert clears that list as well as
    reverting the files.  If any files are specified, revert leaves the list
    of uncommitted merges alone and reverts only the files.  Use ``bzr revert
    .`` in the tree root to revert all files but keep the recorded merges,
    and ``bzr revert --forget-merges`` to clear the pending merge list without
    reverting any files.

    Using "bzr revert --forget-merges", it is possible to apply all of the
    changes from a branch in a single revision.  To do this, perform the merge
    as desired.  Then doing revert with the "--forget-merges" option will keep
    the content of the tree as it was, but it will clear the list of pending
    merges.  The next commit will then contain all of the changes that are
    present in the other branch, but without any other parent revisions.
    Because this technique forgets where these changes originated, it may
    cause additional conflicts on later merges involving the same source and
    target branches.
    RR:tmergetshelveRjs	no-backups&Do not save backups of reverted files.s
forget-mergess8Remove pending merge marker, without changing any files.sfile*cC@setj|ƒ\}}|j|jƒjƒ|rK|j|jƒd ƒn|j||||ƒdS(Ni(RPRŠRöR÷R°RXRt_revert_tree_to_revision(RŒRjR%R[t
forget_mergesR\((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÎs
cC@s6td|d|ƒ}|j|||ddtƒdS(NRR\treport_changes(RkRRRG(R\RjR[R%Ri((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR`×sN(R‘R’R“R˜RR•R”RR!RtstaticmethodR`(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR]s4		tcmd_assert_failcB@seZdZeZd„ZRS(s$Test reporting of assertion failurescC@stdƒ‚dS(Nsalways fails(tAssertionError(RŒ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRäs(R‘R’R“RGR¶R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRdÞstcmd_helpcB@sYeZdZdgZeddƒgZdgZddddgZed
e
d	„ƒZRS(s+Show help on a command or other topic.
    ttopicsRþsShow help on all commands.stopic?R
s--helps-?s-hcC@s;ddl}|dkr'|r'd}n|jj|ƒdS(Nitcommands(tbzrlib.helpRRx(RŒttopicRþR)((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRós	N(R‘R’R“R˜RR•R”R–RRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRfès		tcmd_shell_completecB@s8eZdZdgZdgZeZedd„ƒZ	RS(ssShow appropriate completions for context.

    For a list of all available commands, say 'bzr shell-complete'.
    scontext?ss-ccC@s!ddlm}|j|ƒdS(Ni(t
shellcomplete(R)Rl(RŒRsRl((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRsN(
R‘R’R“R”R–RGR¶RRR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRkûs		tcmd_missingcB@seZdZddgZdgZdeddƒeddƒed	d
ƒeddƒed
dƒdddedddƒeddeddƒeddƒeddeddƒg
Z	dZ
ed e
e
e
d e
e
e
e
e
e
e
d d d dejd„ƒZRS(!sŒShow unmerged/unpulled revisions between two branches.

    OTHER_BRANCH may be local or remote.

    To filter on a range of revisions, you can use the command -r begin..end
    -r revision requests a specific revision, -r ..end or -r begin.. are
    also valid.
            
    :Exit values:
        1 - some missing revisions
        0 - no missing revisions

    :Examples:

        Determine the missing revisions between this and the branch at the
        remembered pull location::

            bzr missing

        Determine the missing revisions between this and another branch::

            bzr missing http://server/branch

        Determine the missing revisions up to a specific revision on the other
        branch::

            bzr missing -r ..-10

        Determine the missing revisions up to a specific revision on this
        branch::

            bzr missing --my-revision ..-10
    R^Rs
other_branch?RrR(sReverse the order of revisions.s	mine-onlys)Display changes in the local branch only.tthissSame as --mine-only.stheirs-onlys*Display changes in the remote branch only.RsSame as --theirs-only.s
log-formatsshow-idsRvRjRxsRFilter on other branch revisions (inclusive). See "help revisionspec" for details.smy-revisionRsRFilter on local branch revisions (inclusive). See "help revisionspec" for details.sinclude-mergeds4Show all revisions in addition to the mainline ones.sinclude-mergesR¶s&Historical alias for --include-merged.Ru.c#@s›ddlm}m}‡fd†}tj|ƒr˜tjjdddddd	d
dˆjƒ|
dkrt|}
q˜t
jtdƒj
ddƒƒ‚n|
dkrt}
n|r¼|}n|rË|}nd
}|ràd}n|rïd}ntj|ƒd}ˆj|jƒjƒ|jƒ}|dkrŽ|}|dkrZt
jtdƒƒ‚ntj|ˆjjƒ}|tdƒj
|ƒƒntj|ƒ}|j|jkr¸|}nˆj|jƒjƒtt||ˆjƒƒƒ}tt||ˆjƒƒƒ}||||d|d|
d|d|ƒ\}}|dkrbtj}|j |ƒ}n|dˆjd|	ddƒ}d} |r|r|t!ddt"|ƒƒt"|ƒƒi}!|j#ƒrÝ|j$j%ƒ}!nx-|||j&|
|!ƒD]}|j'|ƒqöWt(}"d} nt}"|rÅ|rÅ|"t(krH|dƒn|t!ddt"|ƒƒt"|ƒƒ|j#ƒrŒ|j$j%ƒ}!nx-|||j&|
|!ƒD]}|j'|ƒq¥Wd} n|rå|rå|td ƒƒnK|r|r|td!ƒƒn+|p|p|p|s0|td"ƒƒnˆj)ƒ| r—|dkr—|dk	r—ˆj|j*ƒjƒ|jƒdkr—|j+|jƒq—n| S(#Ni(t
find_unmergedtiter_log_revisionsc@s tƒsˆjj|ƒndS(N(R
R‹R£(R¢(RŒ(s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRRs	R·RÃs--include-mergesRÄs--include-mergedRÅs2.5R¸s"{0} and {1} are mutually exclusiveRR~tremotes$No peer location known or specified.s!Using saved parent location: {0}
tbackwardRàtlocal_revid_rangetremote_revid_rangeR†R„R½R³sYou have %d extra revision:
sYou have %d extra revisions:
is


sYou are missing %d revision:
sYou are missing %d revisions:
s"This branch has no new revisions.
s#Other branch has no new revisions.
sBranches are up to date.
(,tbzrlib.missingRoRpRRÐRÌRÍRÎRËRRRcRZR®R!R9RQRöR¬R°RŠR1R‹R‹R·R RRýRÓRCR•RÙRÚRßRbt
supports_tagsR€tget_reverse_tag_dictR«tlog_revisionRGRR…RŽ(#RŒRR(t	mine_onlyttheirs_onlyRÞRþRwRÿR„RvRnRRàRjtmy_revisionRrRåRoRpRtrestricttlocal_branchR·Ržt
remote_branchRsRttlocal_extratremote_extratregistryRëtstatus_codetrev_tag_dictt
printed_local((RŒs3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRIsÎ	
									
				
		
	

		
	


N(R‘R’R“R˜R”RRR	RGR•R—RRR!RRñR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRm
s@!					tcmd_packcB@sAeZdZdgZdgZeddƒgZded„ZRS(s+Compress the data within a repository.

    This operation compresses the data within a bazaar repository. As
    bazaar supports automatic packing of repository, this operation is
    normally not required to be done manually.

    During the pack operation, bazaar takes a backup of existing repository
    data, i.e. pack files. This backup is eventually removed by bazaar
    automatically when it is safe to do so. To save disk space by removing
    the backed up pack files, the --clean-obsolete-packs option may be
    used.

    Warning: If you use --clean-obsolete-packs and your machine crashes
    during or immediately after repacking, you may be left with a state
    where the deletion has been written to disk but the new packs have not
    been. In this case the repository may be unusable.
    Rsbranch_or_repo?sclean-obsolete-packss)Delete obsolete packs to save disk space.R;cC@sftjj|ƒd}y|jƒ}|j}Wn tjk
rQ|jƒ}nX|jd|ƒdS(Nitclean_obsolete_packs(	RRRQRR«RRR×tpack(RŒtbranch_or_repoR†R@R-R«((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRìs
(	R‘R’R“R˜R”RR•R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR…Ós
		tcmd_pluginscB@s)eZdZdgZeed„ƒZRS(s!List the installed plugins.

    This command displays the list of installed plugins including
    version of plugin and a short description of each.

    --verbose shows the path where each plugin is located.

    A plugin is an external component for Bazaar that extends the
    revision control system, by adding or replacing code in Bazaar.
    Plugins can do a variety of things, including overriding commands,
    adding new commands, providing additional network transports and
    customizing log output.

    See the Bazaar Plugin Guide <http://doc.bazaar.canonical.com/plugins/en/>
    for further information on plugins including where to find them and how to
    install them. Instructions are also provided there on how to write new
    plugins using the Python programming language.
    RvcC@s6ddlm}|jjt|jd|ƒƒƒdS(Ni(tplugint
show_paths(R)RŠR‹t
writelinesR>tdescribe_plugins(RŒRvRŠ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs	(R‘R’R“R•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR‰ös	t
cmd_testamentcB@s_eZdZdedddƒedddƒgZdgZdZed	de	e	d
„ƒZ
RS(s,Show testament (signing-form) of a revision.RjRþRxsProduce long-format testament.Ršs"Produce a strict-format testament.sbranch?R¹u.cC@sôddlm}m}|tkr+|}n|}|dkrStj|ƒd}ntj|ƒ}|j|jƒj	ƒ|dkr“|jƒ}	n|dj|ƒ}	|j
|j|	ƒ}
|rÚ|jj|
jƒƒn|jj|
jƒƒdS(Ni(t	TestamenttStrictTestamentR;(tbzrlib.testamentRRRGR9RQR RöR¬R°RRR¯t
from_revisionR«R‹RŒt
as_text_linesR£t
as_short_text(RŒR-RjRþRšRRttestament_classR²RµRÃ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs	N(R‘R’R“RR•R”R—RRR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRŽs		tcmd_annotatecB@sweZdZdddgZdgZedddƒeddd	ƒd
ddgZd
Zee	e	de	dd„ƒZRS(s<Show the origin of each line in a file.

    This prints out the given file with an annotation on the left side
    indicating which revision, author and date introduced the change.

    If the origin is the same for a run of consecutive lines, it is
    shown only at the top, unless the --all option is given.
    tanntblametpraiseR_RRxsShow annotations on all lines.Rþs Show commit date in annotations.Rjsshow-idsRrR¹c

C@sHddlm}t||ƒ\}}	}
|dk	rM|j|jƒjƒn|j|	jƒjƒtd|d|	ƒ}|j|jƒjƒ|dk	r¸|dkr¸|j|
ƒ}n|j|
ƒ}|dkråt	j
|ƒ‚n|dk	r|dkr||||j||d|ƒn%||||j||d|d|	ƒdS(Ni(tannotate_file_treetannotateR-R„(tbzrlib.annotateRšRsRRöR¬R°RkR4RR/R‹(
RŒR_RRþRjR„RrRšR*R-R]R\RN((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRIs"
N(R‘R’R“R–R”RR•R—RR!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR–3s			tcmd_re_signcB@sDeZdZeZdgZddgZdddd„Zd„Z	RS(s4Create a digital signature for an existing revision.srevision_id*RrRju.cC@sŸ|dk	r0|dk	r0tjtdƒƒ‚n|dkr`|dkr`tjtdƒƒ‚ntj|ƒdj}|j|jƒj	ƒ|j
|||ƒS(Ns4You can only supply one of revision_id or --revisions2You must supply either --revision or a revision_idi(RRRcRZRPRQR-RöR…R°R[(RŒtrevision_id_listRjRrR²((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRosc
C@s4ddlj}|j|jƒƒ}|dk	r|jjƒy(x!|D]}|jj||ƒqGWWn|jjƒ‚q0X|jj	ƒn¡|dk	r0t
|ƒdkr|dj|ƒ\}}|jjƒy|jj||ƒWn|jjƒ‚q-X|jj	ƒq0t
|ƒdkr|dj|ƒ\}	}
|dj|ƒ\}}|dkrs|jƒ}n|	dks‹|dkr£t
jtdƒƒ‚n|jjƒy>x7t|	|dƒD]"}|jj|j|ƒ|ƒqÇWWn|jjƒ‚q-X|jj	ƒq0t
jtdƒƒ‚ndS(Niiis5Cannot sign a range of non-revision-history revisionss.Please supply either one revision, or a range.(t
bzrlib.gpgRÕRÖRÔRR«tstart_write_groupt
sign_revisiontabort_write_grouptcommit_write_groupRbR¯RRRcRZR2R6(
RŒR²RžRjRÕtgpg_strategyR±RRµt
from_revnot
from_revidtto_revnotto_revid((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR[xsL






N(
R‘R’R“RGR¶R”R•RRR[(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRgs		tcmd_bindcB@s;eZdZddgZdgZdgZddd„ZRS(s·Convert the current branch into a checkout of the supplied branch.
    If no branch is supplied, rebind to the last bound location.

    Once converted into a checkout, commits must succeed on the master branch
    before they will be applied to the local branch.

    Bound branches use the nickname of its master branch unless it is set
    locally, in which case binding will update the local nickname to be
    that of the master.
    Rõtunbinds	location?Rru.cC@stj|ƒ\}}|dkr®y|jƒ}Wn)tjk
r\tjtdƒƒ‚q®X|dkr®|jƒdk	r“tjtdƒƒ‚q«tjtdƒƒ‚q®ntj	|ƒ}y|j
|ƒWn)tjk
rùtjtdƒƒ‚nX|jƒj
ƒr|j|_ndS(NsCNo location supplied.  This format does not remember old locations.sBranch is already bounds3No location supplied and no previous location knowns?These branches have diverged. Try merging, and then bind again.(R9RQRtget_old_bound_locationRR[RcRZRR R¾tDivergedBranchest
get_configthas_explicit_nicknameR£(RŒR5RrR²R]tb_other((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¸s&N(R‘R’R“R˜R”R•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR©¨s

		t
cmd_unbindcB@s5eZdZddgZgZdgZdd„ZRS(s¨Convert the current checkout into a regular branch.

    After unbinding, the local branch is considered independent and subsequent
    commits will be local only.
    RõR¾Rru.cC@s=tj|ƒ\}}|jƒs9tjtdƒƒ‚ndS(NsLocal branch is not bound(R9RQRªRRcRZ(RŒRrR²R]((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÞs(R‘R’R“R˜R”R•R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR°Ós
	tcmd_uncommitc	B@s›eZdZdgZddedddƒedddƒed	dd
ƒedddƒgZd
gZgZdZde
e
de
e
e
d„Zd„ZRS(sRemove the last committed revision.

    --verbose will print out what is being removed.
    --dry-run will go through all the motions, but not actually
    remove anything.

    If --revision is specified, uncommit revisions to leave the branch at the
    specified revision.  For example, "bzr uncommit -r 15" will leave the
    branch at revision 15.

    Uncommit leaves the working tree ready for a new commit.  The only change
    it may make is to restore any pending merges that were present before
    the commit.
    R‚RvRjsdry-runRxsDon't actually make changes.RësSay yes to all questions.s	keep-tagss*Keep tags that point to removed revisions.R~sAOnly remove the commits from the local branch when in a checkout.s	location?Rc	C@sÕ|dkrd}ntjj|ƒ\}}	y|jƒ}
|
j}Wn/tjtjfk
rwd}
|j	ƒ}nX|
dk	r|j
|
jƒjƒn|j
|jƒjƒ|j
||
||||||ƒS(Nu.(RRRRQR"R-RR#R$RRöR…R°R[(RŒR5R'RvRjRëR~t	keep_tagstcontrolR]R\R²((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs	
c	C@sØddlm}	m}
ddlm}|jƒ\}}
d}|dkrY|}|
}n8|dj|ƒjd}||kr‘|j	|ƒ}n|dks¬t
j|ƒrÆ|jj
tdƒƒdS|	dd|jdd	ƒ}|
||d
tddd
|d|ƒ|r%|jj
tdƒƒn|jj
tdƒƒ|s|tjjtdƒdiƒs||jj
tdƒƒdSntd|
|ƒ||d|d|d
|d|d|d|ƒ|jj
tdƒ|
ƒdS(Ni(t
log_formattertshow_log(RRisNo revisions to uncommit.
RwR†R½R³RvRÄR¦RÆRÇs3Dry-run, pretending to remove the above revisions.
s'The above revision(s) will be removed.
uUncommit these revisionssbzrlib.builtins.uncommits	Canceled
sUncommitting from {%s} to {%s}R\R'RR~R²sAYou can restore the old tip by running:
  bzr pull . -r revid:%s
(RÏR´Rµtbzrlib.uncommitRRRôRR¯RR6RRER‹R£RZR!RÌRÍtconfirm_actionR
(RŒR²R\R'RvRjRëR~R²R´RµRRRøtlast_rev_idRµRRë((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR[sL							
N(
R‘R’R“R˜RR•R”R–R—RR!RR[(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR±äs					tcmd_break_lockcB@sMeZdZdgZedddƒedddƒgZdeed„ZRS(	sÍBreak a dead lock.

    This command breaks a lock on a repository, branch, working directory or
    config file.

    CAUTION: Locks should only be broken when you are sure that the process
    holding the lock has been stopped.

    You can get information on what locks are open via the 'bzr info
    [location]' command.

    :Examples:
        bzr break-lock
        bzr break-lock bzr+ssh://example.com/bzr/foo
        bzr break-lock --conf ~/.bazaar
    s	location?tconfigRxs3LOCATION is the directory where the config lock is.Rës5Do not ask for confirmation before breaking the lock.cC@s£|dkrd}n|r@tjtjditd6ƒt_n|retjd|ƒ}|jƒn:tj	j
|ƒ\}}y|jƒWntk
ržnXdS(Nu.sbzrlib.lockdir.breakR^(RRÌtConfirmationUserInterfacePolicyRÍRGRœtLockableConfigt
break_lockRRRQtNotImplementedError(RŒR5RºRëtconfR³R]((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRns	

N(	R‘R’R“R”RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR¹Ts			tcmd_wait_until_signalledcB@seZdZeZd„ZRS(s“Test helper for test_start_and_stop_bzr_subprocess_send_signal.

    This just prints a line to signal when it is ready, then blocks on stdin.
    cC@s.tjjdƒtjjƒtjjƒdS(Nsrunning
(RƒR„R£Rtstdintreadline(RŒ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRˆs
(R‘R’R“RGR¶R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÀ€st	cmd_servecB@sÂeZdZdgZedddƒedddddd
eƒedddd
eƒedddd
eƒe	dddƒedddƒedd
e
ddƒgZdde
de
ddd„ZRS(sRun the bzr server.tservertinetRxs.Serve on stdin/out for use from inetd or sshd.tprotocolsProtocol to serve.RGsbzrlib.transportttransport_server_registryR!tlistens,Listen for connections on nominated address.RtportsŸListen for connections on nominated port.  Passing 0 as the port number will result in a dynamically allocated port.  The default port depends on the protocol.Rrs!Serve contents of this directory.sallow-writessWBy default the server is a readonly server.  Supplying --allow-writes enables write access to the contents of the served directory and below.  Note that ``bzr serve`` does not perform authentication, so unless some form of external authentication is arranged supplying this option leads to global uncontrolled write access to your file system.sclient-timeouts0Override the default idle client timeout (5min).cC@s”ddlm}|dkr+tjƒ}n|dkrI|jjƒ}n|j|ƒ}	|skd|	}	n|j|	ƒ}
||
||||ƒdS(Ni(R½s	readonly+(	R)R½RR8RøRÇR¿tlocation_to_urltget_transport_from_url(RŒRÈRÉRÅRrtallow_writesRÆtclient_timeoutR½RcRÃ((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR°s
(sbzrlib.transportstransport_server_registryN(R‘R’R“R–RRRGRR‰RtfloatR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÃŽs*							tcmd_joincB@sGeZdZdgZdgZeddddeƒgZed„Z	RS(sCombine a tree into its containing tree.

    This command requires the target tree to be in a rich-root format.

    The TREE argument should be an independent tree, inside another tree, but
    not part of it.  (Such trees can be produced by "bzr split", but also by
    running "bzr branch" with the target inside a tree.)

    The result is a combined tree, with the subtree no longer an independent
    part.  This is marked as a merge of the subtree into the containing tree,
    and all history is preserved.
    R¼R\RLRxsJoin by reference.R¶cC@stj|ƒ}tj|jƒ}tj|ƒd}|jj}|jƒskt	j
tdƒ|fƒ‚n|rÂy|j|ƒWqt	j
k
r¾}t	j
tdƒj||jƒƒ‚qXnNy|j|ƒWn:t	jk
r}t	j
tdƒj||jƒƒ‚nXdS(NisfCan't join trees because %s doesn't support rich root data.
You can use bzr upgrade on the repository.sCannot join {0}.  {1}(RPR RURÁRkRQR-R«tsupports_rich_rootRRcRZt
add_referencetBadReferenceTargetR®treasontsubsumetBadSubsumeSource(RŒR\RLtsub_treet
parent_dirtcontaining_treeRNRý((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÒs&	%(
R‘R’R“R˜R”RRGR•R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÏ¾s
		t	cmd_splitcB@s)eZdZdgZdgZd„ZRS(séSplit a subdirectory of a tree into a separate tree.

    This command will produce a target tree in a format that supports
    rich roots, like 'rich-root' or 'rich-root-pack'.  These formats cannot be
    converted into earlier formats like 'dirstate-tags'.

    The TREE argument should be a subdirectory of a working tree.  That
    subdirectory will be converted into an independent tree, with its own
    branch.  Commits in the top-level tree will not apply to the new subtree.
    R4R\cC@sƒtj|ƒ\}}|j|ƒ}|dkrBtj|ƒ‚ny|j|ƒWn)tjk
r~tj|j	j
ƒ‚nXdS(N(RPRQR4RRR/textracttRootNotRichtRichRootUpgradeRequiredR-R(RŒR\RØR@tsub_id((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRûs(R‘R’R“R˜R”R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÙìs
		tcmd_merge_directivecB@sÎeZdZddgZeZdgZdejddddd	ed
e	ddd
dddƒe
dddƒde
ddeddƒe
ddeddddƒgZdZ
ddde	ddddd„ZRS( sGenerate a merge directive for auto-merge tools.

    A directive requests a merge to be performed, and also provides all the
    information necessary to do so.  This means it must either include a
    revision bundle, or the location of a branch containing the desired
    revision.

    A submit branch (the location to merge into) must be supplied the first
    time the command is issued.  After it has been supplied once, it will
    be remembered as the default.

    A public branch is optional if a revision bundle is supplied, but required
    if --diff or --plain is specified.  It will be remembered as the default
    after the first use.
    ssubmit_branch?spublic_branch?R{Rrs
patch-types.The type of patch to include in the directive.R s
Patch typeR!R"R‡s!Bazaar revision bundle (default).R€sNormal unified diff.tplainsNo patch, just directive.tsignRxsGPG-sign the directive.Rjsmail-toRs9Instead of printing the directive, email to this address.RRyR²s*Message to use when committing this merge.R¹u.c	C@sÀddlm}	m}
ittfd6ttfd6ttfd6|\}}tj|ƒ}
|
jƒ}|dkr}|}n|dkr™|
j	|ƒn|dkr´|
j
ƒ}n|dkrØtjt
dƒƒ‚n|
jƒ}|dkrù|}n|dkr|
j|ƒn|r@|dkr@tjt
dƒƒ‚nd}|dk	rºt|ƒdkr|tjt
d	ƒƒ‚n|d
j|
ƒ}t|ƒdkrÆ|dj|
ƒ}qÆn|
jƒ}|	|ƒ}||
krötjt
dƒƒ‚ntjj|
j|tjƒtjƒ|d|d
|d|d|d|ƒ}|dkrˆ|ro|jj|j|
ƒƒq¼|jj|jƒƒn4|j||
|ƒ}t |
j!ƒƒ}|j"|ƒdS(Ni(RR@RßR€R‡s#No submit branch specified or knowns#No public branch specified or knownis>bzr merge-directive takes at most two one revision identifiersiÿÿÿÿsNo revisions to bundle.t
public_brancht
include_patchtinclude_bundleRRŸ(#RRR@R!RGR9R R?RR@RŠRRcRZR²tset_public_branchRbR¯Rtmerge_directivetMergeDirective2tfrom_objectsR«ttimeRUROR‹R£t	to_signedRŒtto_linestto_emailtSMTPConnectionRÔt
send_email(RŒt
submit_branchRát
patch_typeRàRjtmail_toRRrRR@RâRãR-tstored_submit_branchtstored_public_branchRŸR±t	directiveR¢((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR0s^



				N(R‘R’R“R”RGR¶R˜RR-R!RRR•R—RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÞs,			tcmd_sendcB@seZdZdZddgZddgZedddƒed	dd
ƒedddƒed
dddddeƒeddddddeƒedddƒeddddeƒddeddddeƒeddddd#ƒgZ	d$d$eed$d$d$d$d$d$d$d$d"„ZRS(%sMail or create a merge-directive for submitting changes.

    A merge directive provides many things needed for requesting merges:

    * A machine-readable description of the merge to perform

    * An optional patch that is a preview of the changes requested

    * An optional bundle of revision data, so that the changes can be applied
      directly from the merge directive, without retrieving data from a
      branch.

    `bzr send` creates a compact data set that, when applied using bzr
    merge, has the same effect as merging from the source branch.  
    
    By default the merge directive is self-contained and can be applied to any
    branch containing submit_branch in its ancestory without needing access to
    the source branch.
    
    If --no-bundle is specified, then Bazaar doesn't send the contents of the
    revisions, but only a structured request to merge from the
    public_location.  In that case the public_branch is needed and it must be
    up-to-date and accessible to the recipient.  The public_branch is always
    included if known, so that people can check it later.

    The submit branch defaults to the parent of the source branch, but can be
    overridden.  Both submit branch and public branch will be remembered in
    branch.conf the first time they are used for a particular branch.  The
    source branch defaults to that containing the working directory, but can
    be changed using --from.

    Both the submit branch and the public branch follow the usual behavior with
    respect to --remember: If there is no default location set, the first send
    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 location can be accessed.

    In order to calculate those changes, bzr must analyse the submit branch.
    Therefore it is most efficient for the submit branch to be a local mirror.
    If a public location is known for the submit_branch, that location is used
    in the merge directive.

    The default behaviour is to send the merge directive by mail, unless -o is
    given, in which case it is sent to a file.

    Mail is sent using your preferred mail program.  This should be transparent
    on Windows (it uses MAPI).  On Unix, it requires the xdg-email utility.
    If the preferred client can't be found (or used), your editor will be used.

    To use a specific mail program, set the mail_client configuration option.
    (For Thunderbird 1.5, this works around some bugs.)  Supported values for
    specific clients are "claws", "evolution", "kmail", "mail.app" (MacOS X's
    Mail.app), "mutt", and "thunderbird"; generic options are "default",
    "editor", "emacsclient", "mapi", and "xdg-email".  Plugins may also add
    supported clients.

    If mail is being sent, a to address is required.  This can be supplied
    either on the commandline, by setting the submit_to configuration
    option in the branch itself or the child_submit_to configuration option
    in the submit branch.

    Two formats are currently supported: "4" uses revision bundle format 4 and
    merge directive format 2.  It is significantly faster and smaller than
    older formats.  It is compatible with Bazaar 0.19 and later.  It is the
    default.  "0.9" uses revision bundle format 0.9 and merge directive
    format 1.  It is compatible with Bazaar 0.12 - 0.18.

    The merge directives created by bzr send may be applied using bzr merge or
    bzr pull by specifying a file containing a merge directive as the location.

    bzr send makes extensive use of public locations to map local locations into
    URLs that can be used by other people.  See `bzr help configuration` to
    set them, and use `bzr info` to display them.
    R¹R^Rssubmit_branch?spublic_branch?s	no-bundleRxs/Do not include a bundle in the merge directive.sno-patchs6Do not include a preview patch in the merge directive.R|s"Remember submit and public branch.tfroms]Branch to generate the submission from, rather than the one containing the working directory.RyRRtoutputtosBWrite merge directive to this file or directory; use - for stdout.RšsdRefuse to send if there are uncommitted changes in the working tree, --no-strict disables the check.smail-tos!Mail the request to this address.RjRtbodysBody for the email.R®s Use the specified output format.RGsbzrlib.sendRHc
K@sSddlm}||||||||||
jddƒ|	|
||jd|ƒ
S(Ni(R{RõR;Rš(tbzrlib.sendR{R¿R‹(RŒRîRát	no_bundletno_patchRjR|RöR®RðRRøRštkwargsR{((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÛs	(sbzrlib.sendsformat_registryN(
R‘R’R“R—R˜R”RR0RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRôls<J						tcmd_bundle_revisionscB@sÝeZdZedddƒedddƒedddƒeddd	d
ddeƒed
d
ddddeƒedddƒdedddddƒgZdgZddgZe	Z
ddeededddd„	Z
RS(s–Create a merge-directive for submitting changes.

    A merge directive provides many things needed for requesting merges:

    * A machine-readable description of the merge to perform

    * An optional patch that is a preview of the changes requested

    * An optional bundle of revision data, so that the changes can be applied
      directly from the merge directive, without retrieving data from a
      branch.

    If --no-bundle is specified, then public_branch is needed (and must be
    up-to-date), so that the receiver can perform the merge using the
    public_branch.  The public_branch is always included if known, so that
    people can check it later.

    The submit branch defaults to the parent, but can be overridden.  Both
    submit branch and public branch will be remembered if supplied.

    If a public_branch is known for the submit_branch, that public submit
    branch is used in the merge instructions.  This means that a local mirror
    can be used as your actual submit branch, once you have set public_branch
    for that mirror.

    Two formats are currently supported: "4" uses revision bundle format 4 and
    merge directive format 2.  It is significantly faster and smaller than
    older formats.  It is compatible with Bazaar 0.19 and later.  It is the
    default.  "0.9" uses revision bundle format 0.9 and merge directive
    format 1.  It is compatible with Bazaar 0.12 - 0.18.
    s	no-bundleRxs/Do not include a bundle in the merge directive.sno-patchs6Do not include a preview patch in the merge directive.R|s"Remember submit and public branch.Rõs]Branch to generate the submission from, rather than the one containing the working directory.RyRRRöR÷sWrite directive to this file.RšspRefuse to bundle revisions if there are uncommitted changes in the working tree, --no-strict disables the check.RjR®s Use the specified output format.RGsbzrlib.sendRHR‡R{R^c
K@sh|dkrd}nddlm}||||||||||
jddƒddd|jd|	ƒ
S(Nt-i(R{RõR;Rš(RRùR{R¿R‹(RŒRîRáRúRûRjR|RöR®RšRüR{((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR$s	(sbzrlib.sendsformat_registryN(R‘R’R“RR0RR•R–R˜RGR¶RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRýçs0							tcmd_tagcB@sqeZdZddgZdgZedddƒedddƒed	dd
ƒdgZdddddd
„Z	RS(srCreate, remove or modify a tag naming a revision.

    Tags give human-meaningful names to revisions.  Commands that take a -r
    (--revision) option can be given -rtag:X, where X is any previously
    created tag.

    Tags are stored in the branch.  Tags are copied from one branch to another
    along when you branch, push, pull or merge.

    It is an error to give a tag name that already exists unless you pass
    --force, in which case the tag is moved to point to the new revision.

    To rename a tag (change the name but keep it on the same revsion), run ``bzr
    tag new-name -r tag:old-name`` and then ``bzr tag --delete oldname``.

    If no tag name is specified it will be determined through the 
    'automatic_tag_name' hook. This can e.g. be used to automatically tag
    upstream releases by reading configure.ac. See ``bzr help hooks`` for
    details.
    R‚R€s	tag_name?tdeleteRxs'Delete this tag rather than placing it.Rrs!Branch in which to place the tag.RësReplace existing tags.RjR;c
C@sßtj|ƒ\}}|j|jƒjƒ|r||dkrUtjtdƒƒ‚n|j	j
|ƒttdƒ|ƒn_|rÂt|ƒdkr¬tjtdƒƒ‚n|dj
|ƒ}n|jƒ}|dkr|j|ƒ}|dkrtjtdƒƒ‚qny|j	j|ƒ}	Wntjk
rBd}	nX|rn|	d|fkrntj|ƒ‚n|	|kr‘ttdƒ|ƒnJ|j	j||ƒ|	dkrÇttdƒ|ƒnttd	ƒ|ƒdS(
NsNo tag specified to delete.sDeleted tag %s.is<Tags can only be placed on a single revision, not on a rangeisPlease specify a tag name.s(Tag %s already exists for that revision.sCreated tag %s.sUpdated tag %s.(R9RQRöR…R°RRRcRZR€t
delete_tagRRbR¯Rtautomatic_tag_namet
lookup_tagt	NoSuchTagtTagAlreadyExiststset_tag(
RŒttag_nameRRrRëRjR-R]R±texisting_target((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRTs<		
N(
R‘R’R“R˜R”RRR•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÿ0s					tcmd_tagsc	B@sneZdZdgZedddƒeddddd	dƒdd
gZedde	dd„ƒZ
d„ZRS(s^List tags.

    This command shows a table of tag names and the revisions they reference.
    RcRrRxs&Branch whose tags should be displayed.Rs Sort tags by different criteria.R tSortingRGs
bzrlib.tagttag_sort_methodssshow-idsRjR;cC@sddlm}tj|ƒ\}}|jjƒjƒ}|sDdS|j|jƒj	ƒ|ru|j
||ƒ}n|dkr|jƒ}n|||ƒ|sBxœt
|ƒD]‹\}	\}
}y=|j|ƒ}t|tƒrþdjtt|ƒƒ}nWn)tjtjtjfk
r*d}nX|
|f||	<q°Wn|jƒx.|D]&\}
}
|jjd|
|
fƒqSWdS(Ni(RR;R
s	%-20s %s
(RÊRR9RQR€tget_tag_dicttitemsRöR¬R°t_tags_for_rangeRR¿RÐRRVRãR4RRRR¡tGhostRevisionsHaveNoRevnotUnsupportedOperationRR‹R£(RŒRrRR„RjRR-R]R€RIRcR¥Rtrevspec((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR‘s2


c
C@söt}t|||jƒƒ\}}|j|j}}|rk||krk|jjƒj||ƒrkgSn|jjƒ}g}	xo|j	d|d|ddƒD]O}
|j
|
ddƒ}|rŸ|	jg|D]}||
df^qÎƒqŸqŸW|	S(Ntstart_revision_idtstop_revision_idt	stop_ruletincludei(
RGRÓRCRµR«R=tis_ancestorR€Rwtiter_merge_sorted_revisionsR¿RR(
RŒR-Rjtrange_validRèRétrevid1trevid2t
tagged_revidstfoundRüt
revid_tagsRc((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR³s
1(s
bzrlib.tagstag_sort_methodsN(R‘R’R“R˜RRR•RRR!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR	s			!tcmd_reconfigurecB@s4eZdZddddgZdgZejdddd	d
deded
dddddddƒejdddd	ddededdddƒejdddd	ddededd d!d"ƒe	d#d	d$d%e
ƒe	d&d	d'ƒe	d(d	d)d%eƒe	d*d	d+ƒgZd-d-ed-d-d-d-d-d,„ZRS(.sÏReconfigure the type of a bzr directory.

    A target configuration must be specified.

    For checkouts, the bind-to location will be auto-detected if not specified.
    The order of preference is
    1. For a lightweight checkout, the current bound location.
    2. For branches that used to be checkouts, the previously-bound location.
    3. The push location.
    4. The parent location.
    If none of these is available, --bind-to must be specified.
    tbranchesRõsstandalone-treess
working-treess	location?t	tree_typeR s	Tree typeRxs%The relation between branch and tree.R!R"R-s9Reconfigure to be an unbound branch with no working tree.R\s8Reconfigure to be an unbound branch with a working tree.Rês5Reconfigure to be a bound branch with a working tree.tlightweight_checkoutsAReconfigure to be a lightweight checkout (with no local history).trepository_typesRepository typesLocation fo the repository.R½sJReconfigure to be a standalone branch (i.e. stop using shared repository).t
use_shareds'Reconfigure to use a shared repository.trepository_treessTrees in Repositorys2Whether new branches in the repository have trees.t
with_treessFReconfigure repository to create working trees on branches by default.t
with_no_treessJReconfigure repository to not create working trees on branches by default.sbind-tosBranch to bind checkout to.RRës;Perform reconfiguration even if local changes will be lost.s
stacked-ons5Reconfigure a branch to be stacked on another branch.t	unstackedsYReconfigure a branch to be unstacked.  This may require copying substantial data into it.c	C@s5tjj|ƒ}	|r6|r6tjtdƒƒ‚nA|dk	r[tjƒj	|	|ƒn|rwtj
ƒj	|	ƒn|dkrÃ|dkrÃ|dkrÃ|s§|r«dStjtdƒƒ‚nd}
|dkrêtjj|	ƒ}
ni|dkrtjj
|	ƒ}
nH|dkr/tjj|	|ƒ}
n$|dkrStjj|	|ƒ}
n|
ro|
j	|ƒd}
n|dkrtjj|	ƒ}
n!|dkr±tjj|	ƒ}
n|
rÍ|
j	|ƒd}
n|d	krñtjj|	tƒ}
n$|d
krtjj|	tƒ}
n|
r1|
j	|ƒd}
ndS(Ns+Can't use both --stacked-on and --unstackeds!No target configuration specifiedR-R\Rêslightweight-checkouts
use-sharedR½s
with-treess
with-no-trees(RRR RRcRZRtreconfiguretReconfigureStackedOntapplytReconfigureUnstackedtReconfiguret	to_branchtto_treetto_checkouttto_lightweight_checkoutt
to_use_sharedt
to_standalonetset_repository_treesRGR!(RŒR5tbind_toRëR R"R$RªR'Rrtreconfiguration((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRsV		
	
			
N(R‘R’R“R˜R”RR-RGR!RRR0R•RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRÎsJ						t
cmd_switchc	B@sqeZdZdgZdedddƒdeddd	dd
ƒedddƒgZdeedd
ed„ZRS(s¾Set the branch of a checkout and update.

    For lightweight checkouts, this changes the branch being referenced.
    For heavyweight checkouts, this checks that there are no local commits
    versus the current bound branch, then it makes the local branch a mirror
    of the new location and binds to it.

    In both cases, the working tree is updated and uncommitted changes
    are merged. The user can commit or revert these as they desire.

    Pending merges need to be committed or reverted before using switch.

    The path to the branch to switch to can be specified relative to the parent
    directory of the current branch. For example, if you are currently in a
    checkout of /path/to/branch, specifying 'newbranch' will find a branch at
    /path/to/newbranch.

    Bound branches use the nickname of its master branch unless it is set
    locally, in which case switching will update the local nickname to be
    that of the master.
    sto_location?RrRëRxs*Switch even if local commits will be lost.Rjs
create-branchRyR²s>Create the target branch from this one before switching to it.tstores4Store and restore uncommitted changes in the branch.u.cC@súddlm}|}td|ƒ}g}	tjj|d|	ƒd}
|dkr€|dkrwtjt	dƒƒ‚n|}ny(|
j
d|	ƒ}|jƒjƒ}Wn tj
k
rÊd}t}nX|r1|dkrõtjt	dƒƒ‚nt|
|d|	ƒ}|jj|d|	d|ƒj
ƒ}
nEytj|d|	ƒ}
Wn)tj
k
rut|
|d|	ƒ}
nX|dk	r”|j|
ƒ}n|j|
|
|d|d	|ƒ|rÔ|
j
ƒ}|
j|_ntt	d
ƒtj|
jdƒƒdS(Ni(R¼R¼Rs/You must supply either a revision or a locations*cannot create branch without source branchRÉR±tstore_uncommittedsSwitched to branch: %ssutf-8(R)R¼RfRRRQRRRcRZRRR®RR!R7RDRÕR9R R:R¯R£RR1R‹R(RŒRàRëRYRjRrR7R¼t
tree_locationRRR-thad_explicit_nickR-((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRdsR
			
	

N(	R‘R’R“R”RR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR6@s				tcmd_viewc	B@s€eZdZgZdgZedddƒedddƒedddd	eƒed
ddd	eƒgZeed
d
d„Z
RS(sRManage filtered views.

    Views provide a mask over the tree so that users can focus on
    a subset of a tree when doing their work. After creating a view,
    commands that support a list of files - status, diff, commit, etc -
    effectively have that list of files implicitly given each time.
    An explicit list of files can still be given but those files
    must be within the current view.

    In most cases, a view has a short life-span: it is created to make
    a selected change and is deleted once that change is committed.
    At other times, you may wish to create one or more named views
    and switch between them.

    To disable the current view without deleting it, you can switch to
    the pseudo view called ``off``. This can be useful when you need
    to see the whole tree for an operation or two (e.g. merge) but
    want to switch back to your view after that.

    :Examples:
      To define the current view::

        bzr view file1 dir1 ...

      To list the current view::

        bzr view

      To delete the current view::

        bzr view --delete

      To disable the current view without deleting it::

        bzr view --switch off

      To define a named view and switch to it::

        bzr view --name view-name file1 dir1 ...

      To list a named view::

        bzr view --name view-name

      To delete a named view::

        bzr view --name view-name --delete

      To switch to a named view::

        bzr view --switch view-name

      To list all views defined::

        bzr view --all

      To delete all views::

        bzr view --delete --all
    sfile*RRxs)Apply list or delete action to all views.RsDelete the view.RCs+Name of the view to define, list or delete.RR¼sName of the view to switch to.cC@s—tj|dtƒ\}}|jjƒ\}}|dkrE|}n|r
|ritjtdƒƒ‚q“|r‡tjtdƒƒ‚q“|r¹|jj	diƒ|j
jtdƒƒq“|dkrÝtjtdƒƒ‚q“|jj|ƒ|j
jtdƒ|ƒn‰|rü|r.tjtdƒƒ‚q“|rLtjtdƒƒ‚q“|d	kr¬|dkr|tjtd
ƒƒ‚n|jj	d|ƒ|j
jtdƒ|ƒq“|jj	||ƒtj
|jjƒƒ}	|j
jtdƒj||	ƒƒn—|rœ|rƒ|j
jtd
ƒƒxxt|ƒD]Q}
|
|krFd}nd}tj
||
ƒ}	|j
jd||
|	fƒq+Wq“|j
jtdƒƒn÷|r1|dkr·d}n$|d	krÛtjtdƒƒ‚n|jj|t|ƒƒtj
|jjƒƒ}	|j
jtdƒj||	ƒƒnb|dkrV|j
jtdƒƒn=tj
|jj|ƒƒ}	|j
jtdƒj||	ƒƒdS(NR{s'Both --delete and a file list specifieds$Both --delete and --switch specifiedsDeleted all views.
sNo current view to deletesDeleted '%s' view.
s'Both --switch and a file list specifieds!Both --switch and --all specifiedtoffsNo current view to disablesDisabled '%s' view.
sUsing '{0}' view: {1}
sViews defined:
s=>s  s%s %-20s %s
sNo views defined.
tmys#Cannot change the 'off' pseudo viewsNo current view.
s'{0}' view is: {1}
(RPRŠR!RSRlRRRcRZt
set_view_infoR‹R£tdelete_viewRYRTR®R$tset_view(RŒR[RRRCR¼R\Rot	view_dictR`tviewRò((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRåsr					%	$		%N(R‘R’R“R˜R”RR0R•R!RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR;”s"<					t	cmd_hookscB@seZdZeZd„ZRS(sShow hooks.cC@sæxßttjjƒƒD]È}tj|ƒ}|jjdt|ƒjƒx“t|j	ƒƒD]\}}|jjd|fƒt
|ƒ}|rÄxG|D]&}|jjd|j|ƒfƒq—Wq[|jjtdƒƒq[WqWdS(Ns%s:
s  %s:
s    %s
s    <no hooks installed>
(
R$RQtknown_hooksR%tknown_hooks_key_to_objectR‹R£RR‘R
R>t
get_hook_nameRZ(RŒthook_keyt
some_hookst	hook_namet
hook_pointtfound_hooksthook((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR4s
(R‘R’R“RGR¶R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRC/stcmd_remove_branchcB@sJeZdZdgZdedddƒgZdgZdded„Z	RS(	sîRemove a branch.

    This will remove the branch from the specified location but 
    will keep any working tree or repository in place.

    :Examples:

      Remove the branch at repo/trunk::

        bzr remove-branch repo/trunk

    s	location?RrRëRxs.Remove branch even if it is the active branch.trmbranchcC@s±td|d|ƒ}|rš|jjƒršy|jjddƒ}Wntjk
r`d}nX|dk	rš|j|jkrštjt	dƒƒ‚qšn|jj
|jƒdS(NR<R5RCRƒs+Branch is active. Use --force to remove it.(R>RDRWRRRRR'RcRZtdestroy_branchRC(RŒRrR5RëtbrRð((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRXs
N(
R‘R’R“R”RR•R–RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRMCs		t
cmd_shelvecB@seZdZdgZddedddƒdedd	ejjd
e	de
ƒeddd
ƒedddƒgZddgZde
ddde
e
dd„Zdd„ZRS(s`Temporarily set aside some changes from the current tree.

    Shelve allows you to temporarily put changes you've made "on the shelf",
    ie. out of the way, until a later time when you can bring them back from
    the shelf with the 'unshelve' command.  The changes are stored alongside
    your working tree, and so they aren't propagated along with your branch nor
    will they survive its deletion.

    If shelve --list is specified, previously-shelved changes are listed.

    Shelve is intended to help separate several sets of changes that have
    been inappropriately mingled.  If you just want to get rid of all changes
    and you don't need to restore them later, use revert.  If you want to
    shelve all text changes at once, use shelve --all.

    If filenames are specified, only the changes to those files will be
    shelved. Other files will be left untouched.

    If a revision is specified, changes since that revision will be shelved.

    You can put multiple items on the shelf, and by default, 'unshelve' will
    restore the most recently shelved changes.

    For complicated changes, it is possible to edit the changes in a separate
    editor program to decide what the file remaining in the working copy
    should look like.  To do this, add the configuration option

        change_editor = PROGRAM @new_path @old_path

    where @new_path is replaced with the path of the new version of the 
    file and @old_path is replaced with the path of the old version of 
    the file.  The PROGRAM should save the new file with the desired 
    contents of the file in the working tree.
        
    sfile*RrRjRRxsShelve all changes.RR:s Method to use for writing diffs.R!R"R>sList shelved changes.R5s1Destroy removed changes instead of shelving them.tunshelvet
configurationc	
C@s³|r|jd|ƒSddlm}	|dkrGtjjjƒ}nyP|	j|t	j
ƒ||||d|d|ƒ}
z|
jƒWd|
jƒXWnt
jk
r®dSXdS(NRri(R8R5(trun_for_listtbzrlib.shelf_uiR8RR)RðR7R¿t	from_argsRƒR„RR)Rt	UserAbort(RŒRjRR[RR:R>R5RrR8R;((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRœscC@sÞ|dkrd}ntj|ƒd}|j|jƒjƒ|jƒ}|jƒ}t|ƒdkr|t	t
dƒƒdSx[t|ƒD]M}|j|ƒj
dƒ}|dkr¼d}n|jjd||fƒq‰WdS(Nu.isNo shelved changes.Rs<no message>s%3d: %s
i(RRPRQRöR¬R°Rîtactive_shelvesRbRRZRAtget_metadataR¿R‹R£(RŒRrR\tmanagertshelvestshelf_idR((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRTs		N(R‘R’R“R”RRR)RðR7RGR!R•R˜RRRT(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRQfs #			tcmd_unshelvecB@sweZdZdgZdejddddededd	d
ddd
ddddƒgZdgZ	dddd„ZRS(sñRestore shelved changes.

    By default, the most recently shelved changes are restored. However if you
    specify a shelf by id those changes will be restored instead.  This works
    best when the changes don't depend on each other.
    s	shelf_id?RrRRxsThe action to perform.R"R!R*s(Apply changes and remove from the shelf.R's.Show changes, but do not apply or remove them.RsSInstead of unshelving the changes, show the diff that would result from unshelving.tdelete_onlys%Delete changes without applying them.R$s$Apply changes but don't delete them.R_u.cC@sKddlm}|j||d|ƒ}z|jƒWd|jjƒXdS(Ni(t	UnshelverRr(RUR_RVRR\R°(RŒR\RRrR_t	unshelver((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR×s
N(R‘R’R“R”RR-R!RGR•R˜RR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR]¿s		tcmd_clean_treec	B@s}eZdZdedddƒedddƒedddƒed	dd
ƒedddƒgZeeeeed
d„ZRS(sõRemove unwanted files from working tree.

    By default, only unknown files, not ignored files, are deleted.  Versioned
    files are never deleted.

    Another class is 'detritus', which includes files emitted by bzr during
    normal operations and selftests.  (The value of these files decreases with
    time.)

    If no options are specified, unknown files are deleted.  Otherwise, option
    flags are respected, and may be combined.

    To check what clean-tree will do, use --dry-run.
    RrR.RxsDelete all ignored files.tdetritussJDelete conflict files, merge and revert backups, and failed selftest dirs.Rs&Delete files unknown to bzr (default).sdry-runs.Show files to delete instead of deleting them.RësDo not prompt before deleting.u.cC@sfddlm}|p|p|s+t}n|r:t}n||d|d|d|d|d|ƒdS(Ni(t
clean_treeRR.RbR't	no_prompt(tbzrlib.clean_treeRcRG(RŒRR.RbR'RëRrRc((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRøs		(R‘R’R“RR•R!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRaàs	t
cmd_referencecB@s8eZdZeZddgZddd„Zd„ZRS(s list, view and set branch locations for nested trees.

    If no arguments are provided, lists the branch locations for nested trees.
    If one argument is provided, display the branch location for that tree.
    If two arguments are provided, set the branch location for that tree.
    spath?s	location?c	C@sd}|dk	r|}ntjj|ƒ\}}}|dk	rK|}n|dkrf|jƒ}n|dkrš|jƒjƒ}|j|||ƒnz|j|ƒ}|dkrÇt	j
|ƒ‚n|dkr||j|ƒfg}|j|||ƒn|j|||ƒdS(NR;(
RRRRqRgt_get_all_reference_infoRBt_display_reference_infoR4RR/tget_reference_infotset_reference_info(	RŒRºR5t	branchdirR\R-R]RRN((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRs$		cC@s›g}xW|D]O\}\}}y|j|ƒ}Wntjk
rHnX|j||fƒq
Wx4t|ƒD]&\}}|jjd||fƒqmWdS(Ns%s %s
(R™RtNoSuchIdRR$R‹R£(RŒR\R-Rtref_listRNRºR5((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRh&sN(	R‘R’R“RGR¶R”RRRh(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRfs
tcmd_export_potcB@sMeZdZeZeddddeƒedddƒgZde	d„Z
RS(	s5Export command helps and error messages in po format.RŠRxsHExport help text from named command (defaults to all built in commands).Rsinclude-duplicatessMOutput multiple copies of the same msgid string if it appears more than once.cC@s'ddlm}||j||ƒdS(Ni(t
export_pot(tbzrlib.export_potRoR‹(RŒRŠtinclude_duplicatesRo((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyR?sN(R‘R’R“RGR¶RRR•RR!R(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyRn2s		cC@s¬x¥dgdfdgdfdgdfdgdfd	d
gdfdgdfd
gdfdgdfdgdfdgdfg
D]"\}}}tj|||ƒq‚WdS(Ntcmd_bundle_infosbzrlib.bundle.commandst
cmd_configs
bzrlib.configt	cmd_dpushsbzrlib.foreigntcmd_version_infosbzrlib.cmd_version_infotcmd_resolvetresolvedsbzrlib.conflictst
cmd_conflictstcmd_pingsbzrlib.smart.pingtcmd_sign_my_commitss bzrlib.commit_signature_commandstcmd_verify_signaturestcmd_test_scriptsbzrlib.cmd_test_script(Rt
register_lazy(RCR–tmodule_name((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt_register_lazy_builtinsDs(„R“t
__future__RR8t
bzrlib.bzrdirR)RtglobalsR´RRRt
bzrlib.optionRRRRR	tbzrlib.traceR
RRR
RRRRR+R7R:R>RORaRfRkRpRsRtR™R¸RéRõRÿR	RR1RBRCRTRxR¤R¹RçRôRýRRRR.R0R7R<RCRFRdRpRŠRR–RžR¡R£R¤RÓRýR!RRRRR R2R5R7RBRNRPRR“RšR¡R¥R·RûRÿRR	RNR]RdRfRkRmR…R‰RŽR–RR©R°R±R¹RÀRÃRÏRÙRÞRôRýRÿR	RR6R;RCRMRQR]RaRfRnR(((s3/usr/lib/python2.7/dist-packages/bzrlib/builtins.pyt<module>sì((( 	 	
		g;T+4/9^/<Š’‰–2Jr,6"v>¨		ÿ•	'		uKI	ÿF;AFÛ
ÿ†_O
É# 4A+p,0.f{IOOrT›#Y!#/
-=[ Mr. Bumblebee ]=- _Indonesia_

-=[ Mr. Bumblebee ]=-
_Indonesia_
