# HG changeset patch
# User Steve Losh <steve@stevelosh.com>
# Date 1252709404 14400
# Node ID 862617004f8005f0b1181922eaa4334202929ca8
# Parent  1e7d61653ce054aa6405696fe146ecaed5e8d36d
Add more to the README.

diff -r 1e7d61653ce0 -r 862617004f80 README
--- a/README	Fri Sep 11 18:42:19 2009 -0400
+++ b/README	Fri Sep 11 18:50:04 2009 -0400
@@ -132,6 +132,14 @@
 
 `t` might be simple, but it can do a lot of interesting things.
 
+### Count Your Tasks
+
+Counting your tasks is simple using the `wc` program:
+
+    $ t | wc -l
+          2
+    $
+
 ### Multiple Lists
 
 `t` is for people that want to *do* tasks, not organize them.  With that said, sometimes it's useful to be able to have at least *one* level of organization.  To split up your tasks into different lists you can add a few more aliases:
@@ -150,4 +158,17 @@
 
 Now when you're in your project directory you can use `b` to manage the list of bugs/tasks for that project.  Add the `bugs` file to version control and you're all set.
 
-Even people without `t` installed can view the bug list, because it's plain text.
\ No newline at end of file
+Even people without `t` installed can view the bug list, because it's plain text.
+
+
+Problems, Contributions, Etc
+----------------------------
+
+`t` was hacked together in a couple of nights to fit my needs.  If you use it and find a bug, please let me know.
+
+If you want to request a feature feel free, but remember that `t` is meant to be simple.  If you need anything beyond the basics you might want to look at [todo.txt][] or [TaskWarrior][] instead.  They're great tools with lots of bells and whistles.
+
+If you want to contribute code to `t`, that's great!  Fork the [Mercurial repository][] on BitBucket or the [git mirror][] on GitHub and send me a pull request.
+
+[Mercurial repository]: http://bitbucket.org/sjl/t/
+[git mirror]: http://github.com/sjl/t/
\ No newline at end of file