From 4d057dab603f42ec40b911dbee6792dcf107bd14 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Sun, 13 Dec 2009 06:19:23 -0500 Subject: Converted libbe.storage.vcs.base to new Storage format. --- .../1f9f60de-ba37-42bc-a1c0-dc062ef255e1/body | 25 ---------------------- 1 file changed, 25 deletions(-) delete mode 100644 .be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/1f9f60de-ba37-42bc-a1c0-dc062ef255e1/body (limited to '.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/1f9f60de-ba37-42bc-a1c0-dc062ef255e1/body') diff --git a/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/1f9f60de-ba37-42bc-a1c0-dc062ef255e1/body b/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/1f9f60de-ba37-42bc-a1c0-dc062ef255e1/body deleted file mode 100644 index bd9e63a..0000000 --- a/.be/bugs/12c986be-d19a-4b8b-b1b5-68248ff4d331/comments/1f9f60de-ba37-42bc-a1c0-dc062ef255e1/body +++ /dev/null @@ -1,25 +0,0 @@ -Ronny Pfannschmidt writes: - -> 1. is there any way to aggregate over multiple public branches in -> order to get the complete bug state - -The bug state is as complete as the source code state. It's exactly as -aggregated as the rest of the source code; the “complete bug state” -would be the integration branch where you merge all the feature branches -and bug-fix branches together. - -If instead you want bugs to *not* be tightly linked with the rest of the -source code state, it seems you don't want a distributed bug tracker -like Bugs Everywhere. - --- - \ “I cannot conceive that anybody will require multiplications at | - `\ the rate of 40,000 or even 4,000 per hour …” —F. H. Wales, 1936 | -_o__) | -Ben Finney - - -_______________________________________________ -Be-devel mailing list -Be-devel@bugseverywhere.org -http://void.printf.net/cgi-bin/mailman/listinfo/be-devel -- cgit