Commit | Line | Data |
---|---|---|
1fece88e | 1 | The TODO list before 1.0: |
41a6d859 | 2 | |
aa9b1b9d | 3 | - more regression tests |
83515554 | 4 | - stg help should probably pipe through the $PAGER |
1fece88e CM |
5 | - configurable pull command (currently uses git-pull only) |
6 | - fix StGIT to run correctly in subdirectories | |
7 | - use a separate index for some commands (refresh, fold etc.) so that | |
8 | files already added/removed are not automatically checked in | |
1fece88e CM |
9 | - debian package support |
10 | - man page | |
11 | - document the workflow on the StGIT wiki | |
12 | - maybe a separate undo command rather than passing a --undo option to | |
13 | push and refresh | |
14 | - use same configuration file as GIT | |
41a6d859 CM |
15 | - release 1.0 |
16 | ||
17 | ||
1fece88e | 18 | The future, when time allows or if someone else does them: |
41a6d859 | 19 | |
41a6d859 CM |
20 | - patch dependency tracking |
21 | - multiple heads in a patch - useful for forking a patch, | |
22 | synchronising with other patches (diff format or in other | |
23 | repositories) | |
41a6d859 | 24 | - write bash-completion script for the StGIT commands |
83515554 YD |
25 | - "pull" argument should default to a sane value, "origin" is wrong in |
26 | many cases | |
1fece88e CM |
27 | - commit directly to a patch which is not top |
28 | - patch synchronisation between between branches (as some people, | |
29 | including me have the same patches based on different branches and | |
30 | they have scripts for moving the changes in one to the others) |