Update 2005-09-26 afternoon.
Junio C Hamano committed
Sep 26, 2005 at 16:34 UTC
0103c36d04896d68f92b75f581fdb5cdd6c97956
1 file changed
+24
-6
TODO
+24
-6
@@ -108,12 +108,18 @@ Technical (heavier)
108
skip irrelevant commits.
109
Message-ID: <Pine.LNX.4.63.0509221617300.23242@iabervon.org>
110
111
-* Look at libified GNU diff CVS seems to use.
111
+* Look at libified GNU diff CVS seems to use, or libxdiff.
112
113
114
Technical (milder)
115
------------------
116
117
+* Use 'git-update-ref' in the scripts.
118
+
119
+* Use symbolic refs in .git/HEAD. Should we do that everywhere
120
+ while honoring the symlinked HEAD in the existing repositories
121
+ for backward compatibility, or just only when 'ln -s' fails?
122
+
123
* Revisit 'git-merge'. It probably was a mistake to "loop to
124
choose the best one", since what is best is not ill defined to
125
begin with. This would make it a lot straightforward to
@@ -182,26 +188,38 @@ Technical (milder)
188
189
* Remove obsolete commands [DONE].
190
185
-* Option to limit rename detection for more than N paths [READY].
191
+* Option to limit rename detection for more than N paths [DONE].
192
187
-* Option to show only status and name from diff [READY].
193
+* Option to show only status and name from diff [DONE].
194
195
* What to name the 'master' version between 0.99.7 and 0.99.8
196
and still not break binary distribution folks? 0.99.7z?
197
Pasky gave me a good one: 0.99.7.GIT [DONE]
198
199
+* Listing more than one head on the Pull: line of .git/remotes/
200
+ allows you to make Octopus -- is it useful? Probabaly not.
201
+ Either adopt "only the first head is used for the merge by
202
+ default if taken from .git/remotes/ file", or "list heads to
203
+ merge on a separate Merge: line" proposal. I already have the
204
+ code to do the former, so...
205
+
206
207
Technical (trivial)
208
-------------------
209
197
-* show-branch naming heads is buggy [FIXED].
210
+* Usher SSL enhancements to http-fetch from Nick Hengeveld into
211
+ a shape acceptable by everybody.
212
199
-* Stop installing the old-name symlinks [DONE].
213
+* Require tk 2.4 in the spec file.
214
201
-* 'git add --recursive' [DONE]
215
+* show-branch naming heads is buggy [DONE].
216
+
217
+* Stop installing the old-name symlinks [DONE].
218
219
* 'git merge-projects'?
220
221
+* 'git clone' does not check things out. Should it?
222
+
223
* 'git lost-and-found'? Link dangling commits found by
224
fsck-objects under $GIT_DIR/refs/lost-found/. Then
225
show-branch or gitk can be used to find any lost commit. [A