Update 2005-11-16 before 0.99.9j
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Nov 16, 2005 at 21:59 UTC
97a727dfb7ce3c43d2e3e9c5a5877b6094228739
1 file changed
+16
-10
TODO
+16
-10
@@ -16,6 +16,10 @@ Tool Renames Plan
16
Each of these old-name commands continues to invoke its
17
old-name counterpart on the other end.
18
19
+ - There was a discussion to move bulk of the git-* programs out
20
+ of /usr/bin and use /usr/lib/git; the central mechanism was
21
+ done, but the actual move is postponed post 1.0.
22
+
23
24
What to expect after 0.99.9
25
===========================
@@ -66,7 +70,7 @@ Technical (heavier)
70
magically work from any subdirectory" change by Linus. It is
71
a good change in principle and we would like to have that
72
behaviour but some tool implementations I am sure are assuming
69
- to never run from anywhere other than the top.
73
+ to never run from anywhere other than the top. [Post 1.0]
74
75
* Ref namespace management. Perhaps use refs/local/ suggestion
76
by Linus.
@@ -113,15 +117,14 @@ Technical (milder)
117
------------------
118
119
* Binary package split. Plan laid out and discussion mostly
116
- done.
120
+ done. [RPM side done; Debian side delegated]
121
118
-* User-relative paths by Andreas Ericsson.
122
+* User-relative paths by Andreas Ericsson. [Need to ping]
123
120
-* Proxing git:// connection by Paul Collins.
124
+* Proxing git:// connection by Paul Collins. [Need to ping]
125
126
* Maybe look at Cogito and see if I can help Pasky to adjust to
123
- the later core features? Zack Brown's "cg-seek leaving empty
124
- directories" problem is a good example of this.
127
+ the later core features?
128
129
* Perhaps detect cloning request in upload-pack and cache the
130
result for next cloning request until any of our refs change.
@@ -147,7 +150,7 @@ Technical (milder)
150
* Make rebase restartable; instead of skipping what cannot be
151
automatically forward ported, leave the conflicts in the work
152
tree, have the user resolve it, and then restart from where it
150
- left off [mechanism mostly done].
153
+ left off [mechanism DONE; in pu].
154
155
* Output full path in the "git-rev-list --objects" output, not
156
just the basename, and see the improved clustering results in
@@ -158,7 +161,10 @@ Technical (milder)
161
is what he needs hopefully soon].
162
163
* Make sure we do reasonable thing on binary files even in
161
- cherry-pick and rebase.
164
+ cherry-pick and rebase. [mechanism DONE; rebase in pu]
165
+
166
+* Customizable init-db. Personally I think template mechanism
167
+ is good enough. Otherwise, maybe add hooks/post-init-db.
168
169
170
Technical (trivial)
@@ -175,8 +181,8 @@ Technical (trivial)
181
182
* 'git lost-and-found'? Link dangling commits found by
183
fsck-objects under $GIT_DIR/refs/lost-found/. Then
178
- show-branch or gitk can be used to find any lost commit. [A
179
- feeler patch sent out. Very underwhelming response X-<.]
184
+ show-branch or gitk can be used to find any lost commit.
185
+ [DONE]
186
187
Do not name it /lost+found/; that would probably confuse
188
things that mistake it a mount point (not our code but