-The TODO list for the short term:
+The TODO list until 1.0:
-- tag (snapshot) command
-- pull command (no longer rely on cogito or plain git)
-- log command (it should also show the log per single patch)
-- import command to import a series of patches or a single patch or a
- patch from a different branch in the same tree
-- better help for commands
-- bug reporting tool
-
-
-Other things after the list above is completed:
-
-- fold command (to merge 2 patches into one)
-- automatic e-mail sending with the patches
+- patch revisions support (including a log command)
+- better handling of file renaming
+- use same configuration file as GIT
+- debian package support
+- man page
+- code execution allowed from templates
+- more regression tests
+- stg help should probably pipe through the $PAGER
- release 1.0
-The future, when time allows or someone else does it:
+The future, when time allows or if someone else does it:
-- patches command to show the patches modifying a file
- patch dependency tracking
- multiple heads in a patch - useful for forking a patch,
synchronising with other patches (diff format or in other
repositories)
-- remove the old base of the patch if there are no references to it
- write bash-completion script for the StGIT commands
+- support for branches with / in names
+ (ml: "Handle branch names with slashes")
+- "pull" argument should default to a sane value, "origin" is wrong in
+ many cases
+
+Bugs:
+
+- the following commands break in subdirs:
+ - refresh (ml: "Running StGIT in subdirectories")
+- "stg show" on empty patch shows previous patch
+- "stg add" is accepted when no patch is applied, then any push says
+ one must refresh first, which is obviously wrong
+- "stg add" on files already added should print a notice, so that the
+ user can catch a possible typo
~mdw / stgit / blobdiff