Rev 3037: (John Arbash Meinel, in file:///home/pqm/archives/thelove/bzr/%2Btrunk/
Canonical.com Patch Queue Manager
pqm at pqm.ubuntu.com
Tue Nov 27 20:32:59 GMT 2007
At file:///home/pqm/archives/thelove/bzr/%2Btrunk/
------------------------------------------------------------
revno: 3037
revision-id:pqm at pqm.ubuntu.com-20071127203256-inr45zjrbheqn618
parent: pqm at pqm.ubuntu.com-20071127143838-lkx79x6q91uptc1o
parent: john at arbash-meinel.com-20071127195108-k38ek6apyhxw75fv
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: +trunk
timestamp: Tue 2007-11-27 20:32:56 +0000
message:
(John Arbash Meinel,
bug #59302) Quick audit for single quotes in our documentation.
modified:
bzrlib/builtins.py builtins.py-20050830033751-fc01482b9ca23183
doc/developers/performance-contributing.txt performancecontribut-20070621063612-ac4zhhagjzkr21qp-1
doc/en/mini-tutorial/index.txt index.txt-20070813141352-2u64ooqzo0or4hss-2
doc/en/user-guide/bug_trackers.txt bug_trackers.txt-20070713223459-khxdlcudraii95uv-1
doc/en/user-guide/setting_up_email.txt setting_up_email.txt-20060314161707-fd242c8944346173
------------------------------------------------------------
revno: 3035.1.1
revision-id:john at arbash-meinel.com-20071127195108-k38ek6apyhxw75fv
parent: pqm at pqm.ubuntu.com-20071127101459-zcdf4aia34927kt0
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: doc
timestamp: Tue 2007-11-27 13:51:08 -0600
message:
Address bug #59302 and fix documentation that uses single quotes.
Windows doesn't recognize ' as a quote character.
So documentation should use: bzr foo -m "text" not bzr foo -m 'text'
This patch is just a quick scan of documents for bzr.*', which should
catch most of it.
modified:
bzrlib/builtins.py builtins.py-20050830033751-fc01482b9ca23183
doc/developers/performance-contributing.txt performancecontribut-20070621063612-ac4zhhagjzkr21qp-1
doc/en/mini-tutorial/index.txt index.txt-20070813141352-2u64ooqzo0or4hss-2
doc/en/user-guide/bug_trackers.txt bug_trackers.txt-20070713223459-khxdlcudraii95uv-1
doc/en/user-guide/setting_up_email.txt setting_up_email.txt-20060314161707-fd242c8944346173
=== modified file 'bzrlib/builtins.py'
--- a/bzrlib/builtins.py 2007-11-26 19:50:02 +0000
+++ b/bzrlib/builtins.py 2007-11-27 19:51:08 +0000
@@ -1255,7 +1255,7 @@
bzr init
bzr add .
bzr status
- bzr commit -m 'imported project'
+ bzr commit -m "imported project"
"""
_see_also = ['init-repository', 'branch', 'checkout']
@@ -1915,15 +1915,15 @@
Ignore class files in all directories::
- bzr ignore '*.class'
-
- Ignore .o files under the lib directory::
-
- bzr ignore 'lib/**/*.o'
-
- Ignore .o files under the lib directory::
-
- bzr ignore 'RE:lib/.*\.o'
+ bzr ignore "*.class"
+
+ Ignore .o files under the lib directory::
+
+ bzr ignore "lib/**/*.o"
+
+ Ignore .o files under the lib directory::
+
+ bzr ignore "RE:lib/.*\.o"
"""
_see_also = ['status', 'ignored']
@@ -2444,7 +2444,7 @@
Set the current user::
- bzr whoami 'Frank Chu <fchu at example.com>'
+ bzr whoami "Frank Chu <fchu at example.com>"
"""
takes_options = [ Option('email',
help='Display email address only.'),
=== modified file 'doc/developers/performance-contributing.txt'
--- a/doc/developers/performance-contributing.txt 2007-08-20 03:43:40 +0000
+++ b/doc/developers/performance-contributing.txt 2007-11-27 19:51:08 +0000
@@ -11,7 +11,7 @@
pointing at it that is also BLUE, and start working on that.
Adhoc performance work can also be done. One useful tool is the 'evil' debug
-flag. For instance running ``bzr -Devil commit -m 'test'`` will log a backtrace
+flag. For instance running ``bzr -Devil commit -m "test"`` will log a backtrace
to the bzr log file for every method call which triggers a slow or non-scalable
part of the bzr library. So checking that a given command with ``-Devil`` has
no backtraces logged to the log file is a good way to find problem function
=== modified file 'doc/en/mini-tutorial/index.txt'
--- a/doc/en/mini-tutorial/index.txt 2007-11-04 15:29:17 +0000
+++ b/doc/en/mini-tutorial/index.txt 2007-11-27 19:51:08 +0000
@@ -116,7 +116,7 @@
Commit your work to the Bazaar branch::
- $ bzr commit -m 'Added first line of text'
+ $ bzr commit -m "Added first line of text"
Committed revision 2.
@@ -235,7 +235,7 @@
If you're happy with the changes, you can commit them to your personal
branch::
- $ bzr commit -m 'Merge from main branch'
+ $ bzr commit -m "Merge from main branch"
Committed revision 295.
=== modified file 'doc/en/user-guide/bug_trackers.txt'
--- a/doc/en/user-guide/bug_trackers.txt 2007-08-10 05:17:09 +0000
+++ b/doc/en/user-guide/bug_trackers.txt 2007-11-27 19:51:08 +0000
@@ -13,7 +13,7 @@
When you make a commit you can assiociate it with a bug by using the
``--fixes`` option of ``commit``. For example::
- $ bzr commit --fixes 12345 -m 'Properly close the connection on errors'
+ $ bzr commit --fixes 12345 -m "Properly close the connection on errors"
This will set a revision property on the revision that is committed
which contains the URI at which more information on the bug can be found.
=== modified file 'doc/en/user-guide/setting_up_email.txt'
--- a/doc/en/user-guide/setting_up_email.txt 2007-08-10 05:17:09 +0000
+++ b/doc/en/user-guide/setting_up_email.txt 2007-11-27 19:51:08 +0000
@@ -49,11 +49,11 @@
======================================
You can use the whoami command to set your email globally::
- % bzr whoami 'Joe Cool <joe at example.com>'
+ % bzr whoami "Joe Cool <joe at example.com>"
or only for the current branch::
- % bzr whoami --branch 'Joe Cool <joe at example.com>'
+ % bzr whoami --branch "Joe Cool <joe at example.com>"
These modify your global ``bazaar.conf`` or branch ``branch.conf`` file, respectively.
More information about the bazaar-commits
mailing list