Update post 0.99.7 Signed-off-by: Junio C Hamano <junkio@cox.net>
Update post 0.99.7 Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Sep 22, 2005 at 18:59 UTC
f95c3144f7b076c4e1821ad5a39fc37bf135929e
1 file changed
+38
-37
TODO
+38
-37
@@ -9,45 +9,26 @@ The GIT To-Do File
9
Tool Renames Plan
10
=================
11
12
- - All non-binary commands will lose -script suffix in
13
- $(bindir). The source to git-foo will be either git-foo.sh
14
- or git-foo.perl in the source tree, and the documentation
15
- will be in Documentation/git-foo.txt.
16
-
17
- - The commands whose names have 'cache' to mean 'index file'
18
- will get 'cache' in their names replaced with 'index'. For
19
- git-fsck-cache and git-convert-cache, 'cache' will be
20
- replaced with 'objects'.
21
-
22
- - The commit walkers will have 'pull' in their names replaced
23
- with 'fetch'. 'git-ssh-push' will become 'git-ssh-upload'.
24
-
25
- - We continue to follow the convention to name the C source
26
- file that contains the main program of 'git-foo' command
27
- 'foo.c'. That means we will have 'fsck-objects.c', for
28
- example.
29
-
30
- - At this moment, I am not planning to rename the symbols used
31
- in programs, nor any library sources. "cache.h" will stay
32
- "cache.h", so does "read-cache.c". "struct cache_entry" and
33
- "ce_match_stat()" will keep their names. We _might_ want to
34
- rename them in later rounds but not right now.
35
-
36
- - In 0.99.7, all renamed commands will have symbolic links in
12
+ - In 0.99.7, all renamed commands have symbolic links in
13
$(bindir) so that old names continue to work. These backward
14
compatible names will not appear in documentation. The main
15
documentation, git(7) will talk about the new names but would
16
mention their old names as historical notes. Old environment
17
names defined in gitenv() will also be removed in this release.
18
43
- - In 0.99.8, we do not install these backward compatible
19
+ - In 0.99.8, we will not install these backward compatible
20
symbolic links in $(bindir) anymore. The Makefile will have
21
a target to remove old symlinks from $(DESTDIR)$(bindir) you
22
can run manually to help you clean things up.
23
48
- The timeframe for this is around Oct 1st, but I could be
49
- talked into delaying the symlink removal if Porcelain people
50
- find this schedule too tight.
24
+ As a notable exception, git-ssh-push and git-ssh-pull pair is
25
+ not going away within this timeframe, if ever. Each of these
26
+ old-name commands continues to invoke its old-name
27
+ counterpart on the other end. Updating to 0.99.8 on one end
28
+ of the connection does not requier the other end to update at
29
+ the same time.
30
+
31
+ The timeframe for this is around Oct 1st.
32
33
34
What to expect after 0.99.7
@@ -77,11 +58,19 @@ Documentation
58
* Maybe update tutorial with a toy project that involves two or
59
three developers..
60
61
+* Document octopus [Linus prodded me again; DONE].
62
+
63
* Update tutorial to cover setting up repository hooks to do
64
common tasks.
65
66
* Accept patches to finish missing docs.
67
68
+* Accept patches to talk about "Whoops, it broke. What's
69
+ next?".
70
+
71
+* Accept patches to make formatted tables in asciidoc to work
72
+ well in both html and man pages (see git-diff(1)).
73
+
74
75
Technical (heavier)
76
-------------------
@@ -115,14 +104,24 @@ Technical (heavier)
104
105
* Maybe an Emacs VC backend.
106
107
+* 'git split-projects'? This requires updated 'git-rev-list' to
108
+ skip irrelevant commits.
109
+
110
111
Technical (milder)
112
------------------
113
114
+* Revisit 'git-merge'. It probably was a mistake to "loop to
115
+ choose the best one", since what is best is not ill defined to
116
+ begin with. This would make it a lot straightforward to
117
+ loosen the tree cleanliness requirements to the acceptable
118
+ level.
119
+
120
* The recent commit walker safety patch may be too cautious and
121
appears to take forever when cloning. This may even be
122
infinitely looping in the code lifted from the old rev-list --
125
- needs to be taken a look at [DONE INITIAL CUT].
123
+ needs to be taken a look at [DONE -- and redone very nicely by
124
+ Sergey].
125
126
* Encourage concrete proposals to commit log message templates
127
we discussed some time ago.
@@ -130,7 +129,7 @@ Technical (milder)
129
* Accept patches for more portability.
130
131
* strcasestr() in mailinfo. We may need compat/strcasestr.c;
133
- this is bugging OpenBSD folks.
132
+ this is bugging OpenBSD folks [DONE].
133
134
* Accept patches to cause "read-tree -u" delete a directory when
135
it makes it empty.
@@ -150,10 +149,10 @@ Technical (milder)
149
* Maybe grok PGP signed text/plain in applymbox as well.
150
151
* Perhaps a tool to revert a single file to pre-modification
153
- state? git-cat-file blob `git-ls-files | grep foo` >foo or
154
- git-cat-file blob `git-ls-tree HEAD foo` >foo? What should
155
- the command be called? git-revert is taken so is
156
- git-checkout.
152
+ state? People with BK background know this operation as
153
+ 'clean'. 'git checkout [-f] ent [path...]' was suggested by
154
+ Matthias Urlichs which sounds a natural extention to what the
155
+ command currently does.
156
157
* Enhance "git repack" to not always use --all; this would be
158
handy if the repository contains wagging heads like "pu" in
@@ -174,7 +173,7 @@ Technical (milder)
173
just the basename, and see the improved clustering results in
174
better packing [Tried, but did not work out well].
175
177
-* Remove obsolete commands [READY].
176
+* Remove obsolete commands [DONE].
177
178
* Option to limit rename detection for more than N paths [READY].
179
@@ -184,7 +183,9 @@ Technical (milder)
183
Technical (trivial)
184
-------------------
185
187
-* 'git add --recursive'?
186
+* Stop installing the old-name symlinks.
187
+
188
+* 'git add --recursive' [DONE]
189
190
* 'git merge-projects'?
191