> Don't have time right now, hence that task management application ? ;-)
$ f check out david’s app Ids are updated. On Tue, Aug 17, 2010 at 5:32 PM, Nikhilesh S <s.nikhil...@gmail.com> wrote: > I made a flo-git package for AUR then when I was about to submit I found > that there was already flo-git in AUR. This would have been my first > package. ;_; > > Although I’m the maintainer of that package, I didn’t get to create the PKGBUILD myself. I found another nice way to use flo at work today. When I’m about to work on an item, then I start by removing it off the list. That way I hinder myself to do something else – if I do, then I have to add it back; which I don’t want to. Then I add sub-tasks: $ f 1. commit unchecked code $ f 2. write draft of test for whatever_I_might_be_working_on $ f 3. get Firstname Lastname to code review my test $ f 4. polish $ f 5. test performance of the test $ f 6. see if what I learn from writing this test can improve similar tests $ f 7. commit Then I do the same with these things as I did with the task itself; once I remove an item, then I have to do it. The alias below lists all things that starts with two spaces, followed by one to many digits, a dot, and then a space. It’s pretty solid, as it’s not possible to type in two spaces with flo’s short syntax (nice side effect of how arguments work.) alias ff='flo | grep -E " [[:digit:]]+\. "' Sub-tasks might be overkill in many cases. Managing them might hinder one getting things done… not sure yet… Alexander
