Converted libbe.storage.vcs.base to new Storage format.

1 files changed, 0 insertions, 26 deletions

diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/body
deleted file mode 100644
index ef09dc0..0000000
--- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/6555a651-5a7f-4a8a-9793-47ad1315e9e8/body
+++ /dev/null
@@ -1,26 +0,0 @@
-Hi,
-
-   > For example, let's assume we have target a, b, c There is a way
-   > to know that "a" is a past target, "b" is the current target and
-   > "c" is a future target ?
-
-We could add a "date due" field for each target.
-
-   > More: there is a way to know if a target is closed or open ?
-
-We could add a "target close" operation that moves all open bugs
-assigned to one target to the next date-due target.
-
-I see problems with these ideas in general, because we're assuming
-agreement by all parties/branches on when a target's date due is.
-Maybe it's okay to demand that social conventions be used to handle
-such a disagreement, or maybe not.
-
-- Chris.
--- 
-Chris Ball   <cjb@laptop.org>
-
-_______________________________________________
-Be-devel mailing list
-Be-devel@bugseverywhere.org
-http://void.printf.net/cgi-bin/mailman/listinfo/be-devel