7
Before someone else can get a copy of your work, you need to
8
agree on a transfer technology.
9
You may decide to make the top level directory of your branch
10
a network share, an approach familiar to Windows users.
11
Linux and OS X users might prefer access to be
12
via SFTP, a secure protocol built-in to most SSH servers.
13
Bazaar is *very* flexible in this regard with support for
14
lots of protocols some of which are given below.
16
=========== ======================================================
18
=========== ======================================================
19
file:// Access using the standard filesystem (default)
20
sftp:// Access using SFTP (most SSH servers provide SFTP).
21
bzr:// Fast access using the Bazaar smart server.
22
ftp:// Access using passive FTP.
23
http:// Read-only access to branches exported by a web server.
24
=========== ======================================================
26
As indicated above, branches are identified using URLs with the
27
prefix indicating the transfer technology. If no prefix is given,
28
normal filenames are assumed. For a complete list of supported
29
protocols, see the ``urlspec`` online help topic or the
30
`URL Identifiers <../user-reference/bzr_man.html#url-identifiers>`_
31
section of the Bazaar User Reference.
33
.. _a-reminder-about-shared-repositories:
35
Напоминание о разделяемых репозиториях
36
--------------------------------------
38
Before getting a copy of a branch, have a quick think about
39
where to put it on your filesystem. For maximum storage
40
efficiency down the track, it is recommended that branches
41
be created somewhere under a directory that has been set up
42
as a shared repository. (See `Feature branches`_ in
43
n `Organizing your workspace`_ for a commonly used layout.)
49
You are now ready to grab a branch from someone else and
55
To get a branch based on an existing branch, use the ``branch`` command.
58
bzr branch URL [directory]
60
If a directory is not given, one is created based on the last part of
61
the URL. Here are some examples showing a drive qualified path (M:/) and an
62
sftp URL respectively::
64
bzr branch M:/cool-trunk
65
bzr branch sftp://bill@mary-laptop/cool-repo/cool-trunk
67
This example shows explicitly giving the directory name to use for the
70
bzr branch /home/mary/cool-repo/cool-trunk cool
72
Time and space considerations
73
-----------------------------
75
Depending on the size of the branch being transferred and the
76
speed and latency of the network between your computer and the
77
source branch, this initial transfer might take some time.
78
Subsequent updates should be much faster as only the
79
changes are transferred then.
81
Keep in mind that Bazaar is transferring the
82
complete history of the branch, not just the latest snapshot.
83
As a consequence, you can be off the network (or disconnected
84
from the network share) after ``branch`` completes but you'll
85
still be able to ``log`` and ``diff`` the history of the
86
branch as much as you want. Furthermore, these operations
87
are quick as the history is stored locally.
89
Note that Bazaar uses smart compression technology to
90
minimize the amount of disk space required to store version
91
history. In many cases, the complete history of a project
92
will take up less disk space than the working copy of
95
As explained in later chapters, Bazaar also has support for
96
`lightweight checkouts <#getting-a-lightweight-checkout>`_
97
of a branch, i.e. working trees with
98
no local storage of history. Of course, disconnected usage
99
is not available then but that's a tradeoff you can decide
100
to make if local disk space is really tight for you. Support for
101
limited lookback into history - *history horizons* - is
102
currently under development as well.
104
Viewing branch information
105
--------------------------
107
If you wish to see information about a branch including where it came from,
108
use the ``info`` command. For example::
112
If no branch is given, information on the current branch is displayed.
added
removed
doc/ru/user-guide/branching_a_project.txt
