Rev 6073: Fix the help strings as proposed by jam. in file:///home/vila/src/bzr/experimental/migrate-config-options/

Vincent Ladeuil v.ladeuil+lp at
Mon Aug 15 16:41:38 UTC 2011

At file:///home/vila/src/bzr/experimental/migrate-config-options/

revno: 6073
revision-id: v.ladeuil+lp at
parent: v.ladeuil+lp at
committer: Vincent Ladeuil <v.ladeuil+lp at>
branch nick: migrate-config-options
timestamp: Mon 2011-08-15 18:41:38 +0200
  Fix the help strings as proposed by jam.
-------------- next part --------------
=== modified file 'bzrlib/'
--- a/bzrlib/	2011-08-12 16:25:56 +0000
+++ b/bzrlib/	2011-08-15 16:41:38 +0000
@@ -2385,7 +2385,11 @@
 How many changes before saving the dirstate.
--1 means never save.
+-1 means that we will never rewrite the dirstate file for only
+stat-cache changes. Regardless of this setting, we will always rewrite
+the dirstate file if a file is added/removed/renamed/etc. This flag only
+affects the behavior of updating the dirstate file after we notice that
+a file has been touched.
     Option('dirstate.fdatasync', default=True,
@@ -2422,10 +2426,12 @@
 Steal locks that appears to be dead.
-If set to true, bzr will automatically break locks held by processes from
-the same machine and user that are no longer alive.  Otherwise, it will
-print a message and you can break the lock manually, if you are satisfied
-the object is no longer in use.
+If set to True, bzr will check if a lock is supposed to be held by an
+active process from the same user on the same machine. If the user and
+machine match, but no process with the given PID is active, then bzr
+will automatically break the stale lock, and create a new lock for
+this process.
+Otherwise, bzr will prompt as normal to break the lock.

More information about the bazaar-commits mailing list