From: W. Trevor King <wking@drexel.edu>
Date: Tue, 14 Jul 2009 18:34:40 +0000 (-0400)
Subject: Updated README to match current status.
X-Git-Tag: 1.0.0~63^2~23^2~2
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=c38907c85bbb62a2b3bb00dd05eeb588ecc6845d;p=be.git

Updated README to match current status.

Mostly updated the list of supported VCSs.

Also corrected spacing inconsistency in README.dev.
---

diff --git a/README b/README
index 9562a75..b43c15c 100644
--- a/README
+++ b/README
@@ -1,12 +1,14 @@
 Bugs Everywhere
 ===============
-This is Bugs Everywhere, a bugtracker built on distributed revision control.
-It works with Bazaar and Arch at the moment, but is easily extensible.  It
-can also function with no RCS at all.
+This is Bugs Everywhere, a bugtracker built on distributed revision
+control.  It works with Arch, Bazaar, Darcs, Git, and Mercurial at the
+moment, but is easily extensible.  It can also function with no RCS at
+all.
 
 The idea is to package the bug information with the source code, so that
 bugs can be marked 'fixed' in the branches that fix them.  So, instead of
-numbers, bugs have ids.
+numbers, bugs have globally unique ids.
+
 
 Getting started
 ===============
@@ -15,9 +17,11 @@ set the bug root to your project root, so that Bugs Everywhere works in any
 part of your project tree.
 $ be init $PROJECT_ROOT
 
-To create bugs, use "be new $DESCRIPTION".  To comment on bugs, you can can use
-"be comment $BUG_ID".  To close a bug, use "be close $BUG_ID".  For more
-commands, see "be help".  You can also look at the usage in test_usage.sh.
+To create bugs, use "be new $DESCRIPTION".  To comment on bugs, you
+can can use "be comment $BUG_ID".  To close a bug, use "be close
+$BUG_ID" or "be status $BUG_ID fixed".  For more commands, see "be
+help".  You can also look at the usage examples in test_usage.sh.
+
 
 Using BeWeb, the web UI
 =======================
diff --git a/README.dev b/README.dev
index 644d965..716ce28 100644
--- a/README.dev
+++ b/README.dev
@@ -31,6 +31,7 @@ consistent interface
 
 Again, you can just browse around in becommands to get a feel for things.
 
+
 Testing
 -------