#
#
# patch "wiki/QuickieTasks.mdwn"
#  from [6218370b9e1146588b2c0f65a25ac537e621cd9a]
#    to [2910b3e97a35cd36018c830387b7effd7a4fa161]
#
============================================================
--- wiki/QuickieTasks.mdwn	6218370b9e1146588b2c0f65a25ac537e621cd9a
+++ wiki/QuickieTasks.mdwn	2910b3e97a35cd36018c830387b7effd7a4fa161
@@ -6,9 +6,9 @@ So, here are some smaller tasks, that ve
 
 So, here are some smaller tasks, that very much need doing, that fit the above bill: 
 
- * new commands `mtn detach` (which removes the `_MTN` directory from a workspace), and `mtn attach -r <rev>` (which turns a normal directory into a workspace at the specified location).  These are useful for export/import type workflows.
+ * write a git/svn/hg/<your choice here> importer - presumely git is the most important one nowadays, since most other SCMs can dump their history in git's fast-export format
 
- * new developer's command `mtn make_man_page` that dumps out the --help texts in man page format.  Update build process to use this command to generate a real man page and install it.
+ * new commands `mtn detach` (which removes the `_MTN` directory from a workspace), and `mtn attach -r <rev>` (which turns a normal directory into a workspace at the specified location).  These are useful for export/import type workflows.
 
  * header file audit (only #include things we actually use, use `<iosfwd>` when possible, etc.)
 
@@ -28,17 +28,13 @@ So, here are some smaller tasks, that ve
 
  * script that wraps monotone and gathers statistics on usage, that people could use to help us make UI decisions. Just recording commands would be good; taking notes on things like how many files were edited in a commit, whether any given merge or update had conflicts, etc. would be even cooler.
 
- * make `--debug` output contain timestamps for each event, possibly with another option; this might help provide information about performance issues and where time is being taken between key steps.
-
  * include tests in the test suite to ensure that various external tools (like tailor or buildbot) still work with us; perhaps track their integration code (eg, monotone.py from tailor) and attempt to keep it up to date with changes in HEAD.
 
- * two-argument disapprove: should be some way to apply disapprove to a range of revisions, not just a single one. (basically just means committing the changeset diff(LASTREV,FIRSTREV) as a child of LASTREV.) be careful about merge nodes in the span to disapprove.
-
  * add support for more merge tools -- SVK is one source of these, they support a number that we don't. see SVK/Resolve/* in their source tree.
 
  * add a test for context diff output
 
- * write a test for any bugs in the [tracker](https://savannah.nongnu.org/bugs/index.php?group=monotone) labeled [NEED TEST].
+ * write a test for any bugs in the [tracker](http://code.monotone.ca/p/monotone/issues/label/331/open/) with the tag Task:NeedTest.
 
  * **IN PROGRESS**: Emacs code that makes C-x 4 a drop one into _MTN/log instead of ChangeLog. **See [[ChangeLog]]**