Remove "be set" reference in favour of actual help

Because "be set severity blah" does not actually work, referring users
there to set custom severity levels is just cruel (I spent a half hour
trying to figure out what I was doing wrong). Thus, it is much easier
to, at least for now, state in the help message what they must do in
order to get custom severities and statuses.

diff --git a/libbe/command/severity.py b/libbe/command/severity.py
index c510bc4149e6f2d63ab3750e546d7e497d5ba365..3aea386ce559412b42e25a2f711b9e311650fdda 100644 (file)
--- a/libbe/command/severity.py
+++ b/libbe/command/severity.py
@@ -99,6 +99,18 @@ Severity levels are:
   %s
 
 You can overide the list of allowed severities on a per-repository basis.
-See "be set --help" for more details.
+In order to do so, you must edit your be settings file. This can be found within your .be/xxx-xxx directory.
+
+Add the following lines to override the default severities and use your own:
+
+severities:
+    - - target
+      - The issue is a target or milestone, not a bug.
+    - - wishlist
+      - A feature that could improve usefulness, but not a bug.
+
+You may add as many name/description pairs as you wish to have; they are sorted in order from least important at the top, to most important at the bottom.
+
+Note that the values here _override_ the defaults. That means that if you like the defaults, and wish to keep them, you will have to copy them here before adding any of your own.
 """ % ('\n  '.join(severity_levels))
         return ret

diff --git a/libbe/command/status.py b/libbe/command/status.py
index e034bef4364760d65e821b7a0390398609165583..e708e8fd0252ded8dfbe4667105640b5185001d0 100644 (file)
--- a/libbe/command/status.py
+++ b/libbe/command/status.py
@@ -111,6 +111,24 @@ Inactive status levels are:
   %s
 
 You can overide the list of allowed statuses on a per-repository basis.
-See "be set --help" for more details.
+In order to do so, you must edit your be settings file. This can be found within your .be/xxx-xxx directory.
+
+Add the following lines to override the default statuses and use your own:
+
+active_status:
+    - - unconfirmed
+      - A possible bug which lacks independent existance confirmation.
+    - - open
+      - A working bug that has not been assigned to a developer.
+
+inactive_status:
+    - - closed
+      - The bug is no longer relevant.
+    - - fixed
+      - The bug should no longer occur.
+
+You may add as many name/description pairs as you wish to have; they are sorted in order from most important at the top, to least important at the bottom.
+
+Note that the values here _override_ the defaults. That means that if you like the defaults, and wish to keep them, you will have to copy them here before adding any of your own.
 """ % ('\n  '.join(active_statuses), '\n  '.join(inactive_statuses))
         return ret