Commit | Line | Data |
---|---|---|
1fece88e | 1 | The TODO list before 1.0: |
41a6d859 | 2 | |
aa9b1b9d | 3 | - more regression tests |
2171eff3 | 4 | |
d7eeb79b KH |
5 | - Convert the remaining commands to the new infrastructure. |
6 | ||
7 | - Go through the design of the UI and make sure there's nothing hard | |
8 | to change in there that we'll regret later. | |
9 | ||
10 | - Write a user guide. I'm thinking a document on the order of 10-30 | |
11 | pages that'll explain why one would want to use StGit, and how. | |
12 | ||
13 | - Make sure the rest of the documentation is in good shape. | |
14 | ||
1fece88e CM |
15 | - use a separate index for some commands (refresh, fold etc.) so that |
16 | files already added/removed are not automatically checked in | |
2171eff3 KH |
17 | |
18 | + This is easily done with the new infrastructure. refresh now | |
19 | uses a separate index when appropriate. fold has not yet been | |
20 | converted. | |
21 | ||
41a6d859 CM |
22 | - release 1.0 |
23 | ||
24 | ||
1fece88e | 25 | The future, when time allows or if someone else does them: |
41a6d859 | 26 | |
41a6d859 CM |
27 | - patch dependency tracking |
28 | - multiple heads in a patch - useful for forking a patch, | |
29 | synchronising with other patches (diff format or in other | |
30 | repositories) | |
8741321b YD |
31 | - numeric shortcuts for naming patches near top (eg. +1, -2) |
32 | - (config?) parameter for number of patches included by "series -s" |