Browsing Bosnian translation

2258.

Called with argument StatusHookParams after Bazaar has displayed the
status. StatusHookParams has the attributes (old_tree, new_tree,
to_file, versioned, show_ids, short, verbose). The last four arguments
correspond to the command line options specified by the user for the
status command. to_file is the output stream for writing.

2260.

Called with argument StatusHookParams before Bazaar displays the
status. StatusHookParams has the attributes (old_tree, new_tree,
to_file, versioned, show_ids, short, verbose). The last four arguments
correspond to the command line options specified by the user for the
status command. to_file is the output stream for writing.

2275.

Feature long short line
---------------------- ------------- ------------ -------------------
design goal detailed view concise view 1 revision per line
committer name+email name only name only
author name+email - -
date-time format full date only date only
commit message full full top line
tags yes yes yes
merges indicator - yes -
status/delta optional optional -
diff/patch optional optional -
revision-id optional optional -
branch nick yes - -
foreign vcs properties yes yes -
preferred levels all 1 1
digital signature optional - -

2287.

Trailing slashes on patterns are ignored. If the pattern contains a
slash or is a regular expression, it is compared to the whole path
from the branch root. Otherwise, it is compared to only the last
component of the path. To match a file only in the root directory,
prepend ``./``. Patterns specifying absolute paths are not allowed.

2297.

A revision identifier refers to a specific state of a branch's history. It
can be expressed in several ways. It can begin with a keyword to
unambiguously specify a given lookup type; some examples are 'last:1',
'before:yesterday' and 'submit:'.

2298.

Alternately, it can be given without a keyword, in which case it will be
checked as a revision number, a tag, a revision id, a date specification, or a
branch specification, in that order. For example, 'date:today' could be
written as simply 'today', though if you have a tag called 'today' that will
be found first.

2300.

Ranges are interpreted differently by different commands. To the "log" command,
a range is a sequence of log messages, but to the "diff" command, the range
denotes a change between revisions (and not a sequence of changes). In
addition, "log" considers a closed range whereas "diff" and "merge" consider it
to be open-ended, that is, they include one end but not the other. For example:
"bzr log -r 3647..3649" shows the messages of revisions 3647, 3648 and 3649,
while "bzr diff -r 3647..3649" includes the changes done in revisions 3648 and
3649, but not 3647.

2306.

Supply a specific revision id, that can be used to specify any
revision id in the ancestry of the branch.
Including merges, and pending merges.
Examples::

2309.

Diffing against this shows all the changes that were made in this branch,
and is a good predictor of what merge will do. The submit branch is
used by the bundle and merge directive commands. If no submit branch
is specified, the parent branch is used instead.

2310.

The common ancestor is the last revision that existed in both
branches. Usually this is the branch point, but it could also be
a revision that was merged.