Update 2005-10-02.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Oct 2, 2005 at 21:42 UTC
7b834376cd9138cd92c1cbd0fad1385c9218c20a
1 file changed
+21
-2
TODO
+21
-2
@@ -79,6 +79,14 @@ Technical (heavier)
79
80
* Maybe a pack optimizer.
81
82
+ Given a set of objects and a set of refs (probably a handful
83
+ branch heads and point release tags), find a set of packs to
84
+ allow reasonably minimum download for all of these classes of
85
+ people: (1) somebody cloning the repository from scratch, (2)
86
+ somebody who tends to follow the master branch head reasonably
87
+ closely, (3) somebody who tends to follow only the point
88
+ releases.
89
+
90
* Maybe an Emacs VC backend.
91
92
* 'git split-projects'? This requires updated 'git-rev-list' to
@@ -127,6 +135,12 @@ Technical (milder)
135
repository; experiment if this results in a reasonable
136
workflow, and document it in howto form if it does.
137
138
+ The point is to make it possible to fork that part off to
139
+ somebody else; then I do not have to maintain Documentation
140
+ directory myself anymore, just like I simply slurp the latest
141
+ gitk from Paul and not worry about it ;-).
142
+
143
+
144
* Make rebase restartable; instead of skipping what cannot be
145
automatically forward ported, leave the conflicts in the work
146
tree, have the user resolve it, and then restart from where it
@@ -144,14 +158,19 @@ Technical (milder)
158
Technical (trivial)
159
-------------------
160
147
-* short SHA1 naming is not enforcing uniqueness. Should fix.
161
+* short SHA1 naming is not enforcing uniqueness. Should fix [DONE].
162
149
-* 'git repack' can be DOSed. Should fix.
163
+* 'git repack' can be DOSed. Should fix [DONE].
164
165
* Stop installing the old-name symlinks [POSTPONED].
166
167
* 'git merge-projects'?
168
169
+ Subject: Re: Merges without bases
170
+ References: <1125004228.4110.20.camel@localhost.localdomain>
171
+ Date: Thu, 25 Aug 2005 15:26:36 -0700
172
+ Message-ID: <7vvf1tps9v.fsf@assigned-by-dhcp.cox.net>
173
+
174
* 'git lost-and-found'? Link dangling commits found by
175
fsck-objects under $GIT_DIR/refs/lost-found/. Then
176
show-branch or gitk can be used to find any lost commit. [A