dbb5ae41d406 — "Yann E. MORIN" 8 years ago
bugs: further comment on #71
1 files changed, 15 insertions(+), 1 deletions(-)

M .bugs/details/7154f94cba830e0eadb82c7b22ec8d0970704d0a.txt
M .bugs/details/7154f94cba830e0eadb82c7b22ec8d0970704d0a.txt +15 -1
@@ 128,4 128,18 @@ Wow, thanks for the detailed feedback.  
 
 History browsing, along with quality annotated commits, are both bordering on leaving the "lightweight" model of b.  Not that I terribly mind that happening, but it involves some further consideration and likely refactoring, since the codebase is built up from nice wrappers around a todo list.
 
-This is definitely on *my* todo list now though.  Thanks again.
  No newline at end of file
+This is definitely on *my* todo list now though.  Thanks again.
+
+----
+By: Yann E. MORIN
+On: 2012-05-24 19:11 +0200
+
+Indeed, the template I suggested might be overkill and may be not easy to
+prepare. That was merely a suggestion! ;-)
+
+I see now that the b-commit is not that trivial, when there are two or more
+uncommitted bugs, because the .bugs/bugs file contains the changes for all
+the edited bugs, but b-commit would only commit a single bug.
+
+Anyway, I'll see if I can do something about it (I'm by far no Python
+expert, so don't hold your breath!).