diff options
Diffstat (limited to '.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a')
2 files changed, 28 insertions, 0 deletions
diff --git a/.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a/body b/.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a/body new file mode 100644 index 0000000..777975d --- /dev/null +++ b/.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a/body @@ -0,0 +1,17 @@ +No need for RCS-expansion for the history. If the user is versioning +their code with some RCS, they presumably know how to use the RCS to +investigate the history already. The .be/ directory structure is not +so complicated that it's worth much work to avoid their having to peer +inside it by hand. + +In rare cases where people really do want to peer into history using +only BE or sort by e.g. bug closing time, they could add those +comments by hand, e.g. + $ echo 'bug closed' | be comment <bug> - + $ be close <bug> +So the already-implemented cmp_last_modified would handle it. + +If you want, you could add (optional) comment-generation to the +becommands themselves. For example becommand/merge.py already does +this. + diff --git a/.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a/values b/.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a/values new file mode 100644 index 0000000..47ac983 --- /dev/null +++ b/.be/bugs/9ce2f015-8ea0-43a5-a03d-fc36f6d202fe/comments/4be35966-373b-438c-a35a-824f5c7a940a/values @@ -0,0 +1,11 @@ +Content-type: text/plain + + +Date: Mon, 22 Jun 2009 21:12:00 +0000 + + +From: W. Trevor King <wking@drexel.edu> + + +In-reply-to: d81d0df9-e6d9-4fe8-8dbe-989ef2c81f00 + |