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

1 files changed, 0 insertions, 27 deletions

diff --git a/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/dc32aa62-cf56-4171-84a1-8f7d02b23b6d/body b/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/dc32aa62-cf56-4171-84a1-8f7d02b23b6d/body
deleted file mode 100644
index 3b417be..0000000
--- a/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/dc32aa62-cf56-4171-84a1-8f7d02b23b6d/body
+++ /dev/null
@@ -1,27 +0,0 @@
-On Sat, 2009-07-11 at 08:50 -0400, W. Trevor King wrote:
-> On Sat, Jul 11, 2009 at 01:54:54PM +0200, Ronny Pfannschmidt wrote:
-> > 1. is there any way to aggregate over multiple public branches in order
-> > to get the complete bug state
-> 
-> Keeping the bug data with the source helps synchronize bug state and
-> source code.  Bug state in branch A may not apply to branch B.  Some
-> people like to weaken this source-bug linkage by keeping their bugs in
-> a branch all by themselves (ditz [http://ditz.rubyforge.org/]
-> currently supports this workflow).  It sounds like you want to move
-> from "bugs with code" to "bugs and code in separate branches".  We
-> don't have an easy way to do that in BE at the moment, since
-> version-control systems like Git have a single working branch at a
-> time (I think :p).  What VCS are you using as a backend?
-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
-> 
-> > 2. is there any model for storing bigger files at a central place (for
-> > some of my bugs i have multi-megabyte tarballs attached)
-> 
->   be comment ID "See the tarball at http://yourpage/something.tar.gz"
-> Then to grab the tarball, you'd use:
->   wget `be show COMMENT-ID | sed -n 's/ *See the tarball at //p'`
-> to grab it.
-so the basic idea is to do it completely self-managed and have have
-heterogenous sources of extended data?