|
271.
|
|
|
See ``bzr help revisionspec`` for details on how to specify X and Y.
Some common examples are given below::
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
Siehe ``bzr help revisionspec`` für Informationen dazu, wie X und Y angegeben werden.
Es folgen ein paar allgemeine Beispiele::
|
|
Translated and reviewed by
Hendrik Schrieber
|
|
|
|
Located in
bzrlib/builtins.py:2525
|
|
272.
|
|
|
-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
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2528
|
|
273.
|
|
|
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.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2535
|
|
274.
|
|
|
:Path filtering:
|
|
|
|
:Pfad-Filtern:
|
|
Translated and reviewed by
Dennis Baudys
|
|
|
|
Located in
bzrlib/builtins.py:2542
|
|
275.
|
|
|
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.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2544
|
|
276.
|
|
|
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.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2548
|
|
277.
|
|
|
Historical context is also important when interpreting pathnames of
renamed files/directories. Consider the following example:
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2552
|
|
278.
|
|
|
* revision 1: add tutorial.txt
* revision 2: modify tutorial.txt
* revision 3: rename tutorial.txt to guide.txt; add tutorial.txt
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2555
|
|
279.
|
|
|
In this case:
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
In diesem Fall:
|
|
Translated and reviewed by
Dennis Baudys
|
|
|
|
Located in
bzrlib/builtins.py:2559
|
|
280.
|
|
|
* ``bzr log guide.txt`` will log the file added in revision 1
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
bzrlib/builtins.py:2561
|