aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a
diff options
context:
space:
mode:
authorW. Trevor King <wking@drexel.edu>2009-12-13 06:19:23 -0500
committerW. Trevor King <wking@drexel.edu>2009-12-13 06:19:23 -0500
commit4d057dab603f42ec40b911dbee6792dcf107bd14 (patch)
tree9a73459aa160e3c96f4893b132543f412ca6e97f /.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a
parentdff6bd9bf89ca80e2265696a478e540476718c9c (diff)
downloadbugseverywhere-4d057dab603f42ec40b911dbee6792dcf107bd14.tar.gz
Converted libbe.storage.vcs.base to new Storage format.
Diffstat (limited to '.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a')
-rw-r--r--.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body47
-rw-r--r--.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values14
2 files changed, 0 insertions, 61 deletions
diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body
deleted file mode 100644
index c799630..0000000
--- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/body
+++ /dev/null
@@ -1,47 +0,0 @@
-On Sunday 19 July 2009 00:00:46 Chris Ball wrote:
-> 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.
-
-Good idea
-
-> > 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.
-
-Nice. But instead of moving all bugs to the next date-due target, I'd prefer
-to leave the choice to the user
-
-
-> 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.
-
-I don't see these as problems per se. We can have two cases:
-
-1) a personal branch (like my html output or Trevor's email interface). In
-this case there is not any problem to decide the due date
-
-2) a branch with a group of delopers (let it be the canonical branch o an
-experimental branch): in this case I suppose that working together means to be
-able to agree on some things
-
-In any case, having the possibility to set a due date does not means that it
-is obligatory to do it and should be a good idea to offer as many possibilities
-as we can to the users of BE
-
-bye
-Gianluca
-
-
-
-_______________________________________________
-Be-devel mailing list
-Be-devel@bugseverywhere.org
-http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
diff --git a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values b/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values
deleted file mode 100644
index 5b9011f..0000000
--- a/.be/bugs/22b6f620-d2f7-42a5-a02e-145733a4e366/comments/4952e1c7-e035-42f1-882b-6b5264481d0a/values
+++ /dev/null
@@ -1,14 +0,0 @@
-Alt-id: <200907202259.11774.gian@grys.it>
-
-
-Author: Gianluca Montecchi <gian@grys.it>
-
-
-Content-type: text/plain
-
-
-Date: Mon, 20 Jul 2009 22:59:11 +0200
-
-
-In-reply-to: 6555a651-5a7f-4a8a-9793-47ad1315e9e8
-