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

1 files changed, 0 insertions, 33 deletions

diff --git a/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/d86e497d-667d-4c2b-9249-76026df56633/body b/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/d86e497d-667d-4c2b-9249-76026df56633/body
deleted file mode 100644
index 93f082b..0000000
--- a/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/d86e497d-667d-4c2b-9249-76026df56633/body
+++ /dev/null
@@ -1,33 +0,0 @@
-On Sat, 2009-07-11 at 23:34 +1000, Ben Finney wrote:
-> Ronny Pfannschmidt <Ronny.Pfannschmidt@gmx.de> writes:
-> 
-> > the basic idea is to take a look at all public branches (for exaple
-> > all on lp/bitbucket/github) in order to tell the user of a
-> > webinterface that bug foo is fixed in branch xyz, and if its merged to
-> > the main branch
-> 
-> I don't understand. The state of the bug in the main branch is right
-> there in the main branch; if it's not fixed there, it's not fixed there.
-> If it's merged in from a different branch, the bug state follows all the
-> other changes when they come in.
-> 
-> Can you give an example of what would be done differently?
-> 
-i want to see the combination of the bug data of all branches
-
-for example
-
-i got bug
-its fixed in the branch "something"
-its not fixed/merged to "main"
-
-now something like a website should tell me, this bug has been fixed in
-branch xyz and the fix is not yet merged into main
-
-
-
-
-_______________________________________________
-Be-devel mailing list
-Be-devel@bugseverywhere.org
-http://void.printf.net/cgi-bin/mailman/listinfo/be-devel