Anonymous avatar Anonymous committed dbb5ae4

bugs: further comment on #71

Comments (0)

Files changed (1)

.bugs/details/7154f94cba830e0eadb82c7b22ec8d0970704d0a.txt

 
 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.
+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!).
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.