Keep track of to-do document.
This is written in a form of to-do list for me, so if I say "accept patch", it means I do not currently plan to do that myself. People interested in seeing it materialize please take a hint. Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Aug 26, 2005 at 00:32 UTC
1bd90415deccc4562e0fb4d0f8e58140aa687ac1
1 file changed
+95
TODO
new
+95
@@ -0,0 +1,95 @@
1
+What to expect after 0.99.5
2
+===========================
3
+
4
+This is written in a form of to-do list for me, so if I say
5
+"accept patch", it means I do not currently plan to do that
6
+myself. People interested in seeing it materialize please take
7
+a hint.
8
+
9
+
10
+Documentation
11
+-------------
12
+
13
+* Accept patches from people who actually have done CVS
14
+ migration and update the cvs-migration documentation.
15
+ Link the documentation from the main git.txt page.
16
+
17
+* Update the SubmittingPatches document to add MUA specific
18
+ hints on how to disable unwanted MIME and flowed-text by
19
+ collecting past list postings. Accept patches from people who
20
+ was hit by shiny blue bat to update the same.
21
+
22
+* Talk about using rsync just once at the beginning when
23
+ initializing a remote repository so that local packs do not
24
+ need to be expanded. I personally do not think we need tool
25
+ support for this.
26
+
27
+* Update tutorial to cover shared repository style a bit more,
28
+ maybe with a toy project that involves two or three
29
+ repositories.
30
+
31
+* Update tutorial to cover setting up repository hooks to do
32
+ common tasks.
33
+
34
+* Get help to properly use asciidoc in tutorial.
35
+
36
+* Maybe justify and demonstrate an Octopus in the tutorial. Add
37
+ it to the glossary.
38
+
39
+
40
+Technical (heavier)
41
+-------------------
42
+
43
+* Tony Luck reported an unfortunate glitch in the 3-way merge.
44
+ Encourage discussions to come up with a not-so-expensive way
45
+ to catch the kind of ambiguities that led to his misery.
46
+
47
+
48
+Technical (milder)
49
+------------------
50
+
51
+* When the branch head pointed by $GIT_DIR/HEAD changes while
52
+ the index file and working tree are looking the other way
53
+ (e.g. somebody pushed into your repository, or you ran "git
54
+ fetch" to update the ref your working tree is on), "git
55
+ checkout" without -f gets confused. Figure out a good way to
56
+ handle this.
57
+
58
+* "git commit -m" should work for initial commits and perhaps
59
+ merge commits as well. Warning about merge is still a good
60
+ thing to do, while -m is useful in scripted non-interactive
61
+ use, so we need to be careful.
62
+
63
+* Encourage concrete proposals to commit log message templates
64
+ we discussed some time ago.
65
+
66
+* Bug Ryan and work with him to update send-email easier to use.
67
+
68
+* Look at portability fixes from Jason Riedy
69
+
70
+ http://www.cs.berkeley.edu/~ejr/gits/git.git#portable
71
+
72
+* Accept patches to cause "read-tree -u" delete a directory when
73
+ it makes it empty.
74
+
75
+* Perhaps accept patches to introduce the concept of "patch flow
76
+ expressed as ref mappings" Josef has been advocating about.
77
+
78
+* MIMEified applymbox to grok B and Q encodings in headers and
79
+ turn them into UTF-8; unwrap QP; explode multipart.
80
+
81
+* "git cherry-pick" that applies the patch an existing commit
82
+ introduces in its ancestry chain, possibly using the 3-way
83
+ merge machinery; update rebase using the cherry-pick command.
84
+ Carl's redo/undo might fall out naturally from this.
85
+
86
+* A tool to detect, show and prune already merged topic
87
+ branches.
88
+
89
+* Perhaps "git branch -d" to delete a branch.
90
+
91
+* Enhance "git repack" to not always use --all; this would be
92
+ handy if the repository contains wagging heads like "pu" in
93
+ git.git repository.
94
+
95
+* Remove "git clone-dumb-http".