Merge lp:~toonn/bzr/log-bzr-version into lp:bzr

Proposed by Toon Nolten
Status: Merged
Approved by: Andrew Bennetts
Approved revision: not available
Merged at revision: not available
Proposed branch: lp:~toonn/bzr/log-bzr-version
Merge into: lp:bzr
Diff against target: 31 lines (+3/-2)
2 files modified
bzrlib/commands.py (+1/-0)
doc/developers/HACKING.txt (+2/-2)
To merge this branch: bzr merge lp:~toonn/bzr/log-bzr-version
Reviewer Review Type Date Requested Status
Andrew Bennetts Approve
Toon Nolten (community) Needs Resubmitting
Review via email: mp+16660@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Toon Nolten (toonn) wrote :

**Why**
    Solution to https://bugs.launchpad.net/bzr/+bug/257170

**How**
    I added one line to commands.py, the first line after the docstring of run_bzr:
    trace.mutter("bazaar version: " + bzrlib.__version__)

**Anything else you may have fixed in passing**
    I corrected two (supposed) typos in HACKING.txt.

Revision history for this message
Andrew Bennetts (spiv) wrote :

Thanks for the patch! It looks good. My only comment on it is: don't add a blank line after the trace.mutter, we generally don't use much vertical whitespace within functions. The typo fixes look good too.

Have you already executed the Canonical contribution agreement? If not, could you please do so according to <http://www.canonical.com/contributors> — thanks.

review: Needs Fixing
Revision history for this message
Toon Nolten (toonn) wrote :

I removed the vertical whitespace, thank you for the quick review.

I didn't know about the contribution agreement yet, thank you for the information.

review: Needs Resubmitting
Revision history for this message
Andrew Bennetts (spiv) wrote :

Thanks for taking care of the agreement and tidying that whitespace. It all looks good to me now.

Ordinarily we get two committers to review patches before landing them, but this is sufficiently small and safe that I'm happy to send this to PQM without further review. I just realised it lacks a NEWS entry (you deserve credit for your effort, after all!), but I'll happily take care of that now then land it.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'bzrlib/commands.py'
2--- bzrlib/commands.py 2009-12-09 05:47:32 +0000
3+++ bzrlib/commands.py 2010-01-04 18:21:15 +0000
4@@ -927,6 +927,7 @@
5 --concurrency
6 Specify the number of processes that can be run concurrently (selftest).
7 """
8+ trace.mutter("bazaar version: " + bzrlib.__version__)
9 argv = list(argv)
10 trace.mutter("bzr arguments: %r", argv)
11
12
13=== modified file 'doc/developers/HACKING.txt'
14--- doc/developers/HACKING.txt 2009-12-02 20:34:07 +0000
15+++ doc/developers/HACKING.txt 2010-01-04 18:21:15 +0000
16@@ -62,7 +62,7 @@
17 to involving the community before you spend much time on a change.
18 These include:
19
20-* you get to build on the wisdom on others, saving time
21+* you get to build on the wisdom of others, saving time
22
23 * if others can direct you to similar code, it minimises the work to be done
24
25@@ -680,7 +680,7 @@
26 ``only_raises`` decorator (from ``bzrlib.decorators``) for methods that
27 are typically called in ``finally`` blocks, such as ``unlock`` methods.
28 For example, ``@only_raises(LockNotHeld, LockBroken)``. All errors that
29-are unlikely to be a knock-on failure from an previous failure should be
30+are unlikely to be a knock-on failure from a previous failure should be
31 allowed.
32
33