As of 1.0rc4
Revamp TODO list and stop HAVEDONE (does not make sense to list everything since 0.99). Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Dec 4, 2005 at 23:41 UTC
52dd75885cd3a78dcb3d7f4f0ddf16f4b8f62b56
2 files changed
+31
-202
HAVEDONE
deleted
-96
@@ -1,96 +0,0 @@
1
-Done in 0.99.9
2
-==============
3
-
4
-Ports
5
-~~~~~
6
-
7
-* Cygwin port [HPA].
8
-
9
-* OpenBSD build [Merlyn and others].
10
-
11
-
12
-Fixes
13
-~~~~~
14
-
15
-* clone request over git native protocol from a repository with
16
- too many refs did not work; this has been fixed.
17
-
18
-* git-daemon got safer for kernel.org use [HPA].
19
-
20
-* Extended SHA1 parser was not enforcing uniqueness for
21
- abbreviated SHA1; this has been fixed.
22
-
23
-* http transport does not barf on funny characters in URL.
24
-
25
-* The ref naming restrictions have been formalized and the
26
- coreish refuses to create funny refs; we still need to audit
27
- importers. See git-check-ref-format(1).
28
-
29
-
30
-New Features and Commands
31
-~~~~~~~~~~~~~~~~~~~~~~~~~
32
-
33
-* .git/config file as a per-repository configuration mechanism,
34
- and some commands understand it [Linus]. See
35
- git(7).
36
-
37
-* The core.filemode configuration item can be used to make us a
38
- bit more FAT friendly. See git(7).
39
-
40
-* The extended SHA1 notation acquired Peel-the-onion operator
41
- ^{type} and ^{}. See git-rev-parse(1).
42
-
43
-* SVN importer [Matthias]. See git-svnimport(1).
44
-
45
-* .git/objects/[0-9a-f]{2} directories are created on demand,
46
- and removed when becomes empty after prune-packed [Linus].
47
-
48
-* Filenames output from various commands without -z option are
49
- quoted when they embed funny characters (TAB and LF) using
50
- C-style quoting within double-quotes, to match the proposed
51
- GNU diff/patch notation [me, but many people contributed in
52
- the discussion].
53
-
54
-* git-mv is expected to be a better replacement for git-rename.
55
- While the latter has two parameter restriction, it acts more
56
- like the regular 'mv' that can move multiple things to one
57
- destinatino directory [Josef Weidendorfer].
58
-
59
-* git-checkout can take filenames to revert the changes to
60
- them. See git-checkout(1)
61
-
62
-* The new program git-am is a replacement for git-applymbox that
63
- has saner command line options and a bit easier to use when a
64
- patch does not apply cleanly.
65
-
66
-* git-ls-remote can show unwrapped onions using ^{} notation, to
67
- help Cogito to track tags.
68
-
69
-* git-merge-recursive backend can merge unrelated projects.
70
-
71
-* git-clone over native transport leaves the result packed.
72
-
73
-* git-http-fetch issues multiple requests in parallel when
74
- underlying cURL library supports it [Nick and Daniel].
75
-
76
-* git-fetch-pack and git-upload-pack try harder to figure out
77
- better common commits [Johannes].
78
-
79
-* git-read-tree -u removes a directory when it makes it empty.
80
-
81
-* git-diff-* records abbreviated SHA1 names of original and
82
- resulting blob; this sometimes helps to apply otherwise an
83
- unapplicable patch by falling back to 3-way merge.
84
-
85
-* git-format-patch now takes series of from..to rev ranges and
86
- with '-m --stdout', writes them out to the standard output.
87
- This can be piped to 'git-am' to implement cheaper
88
- cherry-picking.
89
-
90
-* git-tag takes '-u' to specify the tag signer identity [Linus].
91
-
92
-* git-rev-list can take optional pathspecs to skip commits that
93
- do not touch them (--dense) [Linus].
94
-
95
-* Comes with new and improved gitk [Paulus and Linus].
96
-
TODO
+31
-106
@@ -6,23 +6,8 @@ The GIT To-Do File
6
http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO
7
8
9
-Tool Renames Plan
10
-=================
11
-
12
- - Immedately after 0.99.9, the backward compatible symbolic
13
- links in $(bindir) will be removed [DONE].
14
-
15
- git-ssh-push and git-ssh-pull pair is not going away if ever.
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
-===========================
9
+What to expect until 1.0
10
+========================
11
12
This is written in a form of to-do list for me, so if I say
13
"accept patch", it means I do not currently plan to do that
@@ -31,13 +16,12 @@ a hint. Also whatever I marked "Perhaps" do not have to happen
16
if ever -- only if somebody cares enough and submits a clean
17
patch, perhaps ;-).
18
19
+Only handful things remain until 1.0.
20
+
21
22
Documentation
23
-------------
24
38
-* Help Jon Loeliger to find place in the documentation to place
39
- his drawing [DONE].
40
-
25
* Accept patches from people who actually have done CVS
26
migration and update the cvs-migration documentation.
27
Link the documentation from the main git.txt page.
@@ -57,33 +41,18 @@ Documentation
41
them.
42
43
* Accept patches to talk about "Whoops, it broke. What's
60
- next?" [Started].
44
+ next?" [ONGOING].
45
46
* Accept patches to make formatted tables in asciidoc to work
47
well in both html and man pages (see git-diff(1)).
48
49
+* Work around multiple synopses lines in manual pages
50
+ (e.g. git-bisect).
51
+
52
53
Technical (heavier)
54
-------------------
55
69
-* Assess the side effects of "make the rest of the things
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
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.
77
-
78
-* Git daemon, when deployed at kernel.org, might turn out to be
79
- quite a burden, since it needs to generate customized packs
80
- every time a new request comes in. It may be worthwhile to
81
- precompute some packs for popular sets of heads downloaders
82
- have and serve that, even if that could give more than the
83
- client asks for in some cases. We will know about this soon
84
- enough [DONE part to allow using precomputed pack, but not
85
- dynamic caching part].
86
-
56
* Libification. There are many places "run once" mentality is
57
ingrained in the management of basic data structures, which
58
need to be fixed. [Matthias Urlichs is already working on
@@ -100,48 +69,49 @@ Technical (heavier)
69
closely, (3) somebody who tends to follow only the point
70
releases.
71
103
-* Maybe an Emacs VC backend.
72
+ This needs a matching smart on the dumb protocol downloader.
73
105
-* 'git split-projects'? This requires updated 'git-rev-list' to
106
- skip irrelevant commits.
107
- Message-ID: <Pine.LNX.4.63.0509221617300.23242@iabervon.org>
74
+* Maybe an Emacs VC backend.
75
76
* Look at libified GNU diff CVS seems to use, or libxdiff.
77
[Daniel has his own diff tool almost ready to start
78
integrating and testing; Post 1.0]
79
113
-* Plug-in file-level merges [Post 1.0].
80
+* Plug-in file-level merges [Post 1.0]. On the other hand, we
81
+ may not even need this; just tell people to run "xxdiff -U" on
82
+ the working tree files.
83
+
84
+* Ref namespace management. Perhaps use refs/local/ suggestion
85
+ by Linus. [Does not seem to be high on people's priority list,
86
+ and not interested myself. People can resurrect this
87
+ discussion if they want.]
88
89
90
Technical (milder)
91
------------------
92
93
+* strip leading directory from ls-tree output.
94
+
95
+* diff stopping at the first output; qgit wants to know if this
96
+ tree has any A or D from the other tree and nothing else.
97
+ Would help internal tree-diff in rev-list as well [can be post
98
+ 1.0].
99
+
100
* merge-recursive needs to register conflicting paths as higher
101
stage entries in the index. For that, it first needs to
102
construct three trees whose paths are already renamed, and
122
- call 3-way read-tree.
103
+ call 3-way read-tree. Alternatively, update-index needs to
104
+ give it a way to construct higher stages [can be post 1.0, but
105
+ nicer to have in 1.0].
106
124
-* Binary package split. Plan laid out and discussion mostly
125
- done. [RPM side done; Debian side delegated]
126
-
127
-* User-relative paths by Andreas Ericsson. [DONE]
128
-
129
-* Accessing configuration variables from C and from scripts by
130
- Johannes [DONE].
107
+* daemon --strict-symlink [can be post 1.0].
108
132
-* Proxing git:// connection by Paul Collins. [DONE]
133
-
134
-* Maybe look at Cogito and see if I can help Pasky to adjust to
135
- the later core features?
109
+* Binary package split. Plan laid out and discussion mostly
110
+ done. [RPM side done; Debian side thrown over the wall.]
111
112
* Perhaps detect cloning request in upload-pack and cache the
113
result for next cloning request until any of our refs change.
114
140
-* Encourage concrete proposals to commit log message templates
141
- we discussed some time ago.
142
-
143
-* Perhaps accept patches to do undo/redo.
144
-
115
* Perhaps accept patch to optionally allow '--fuzz' in
116
'git-apply'.
117
@@ -155,59 +125,14 @@ Technical (milder)
125
handy if the repository contains wagging heads like "pu" in
126
git.git repository.
127
158
-* Make rebase restartable; instead of skipping what cannot be
159
- automatically forward ported, leave the conflicts in the work
160
- tree, have the user resolve it, and then restart from where it
161
- left off [DONE].
162
-
128
* Output full path in the "git-rev-list --objects" output, not
129
just the basename, and see the improved clustering results in
130
better packing [Tried, but did not work out well].
131
167
-* Updated git-changes-script Jeff Garzik needs [Not needed --
168
- pull into local or borrow temporarily with alternate object
169
- directories environment variable and use normal tools].
170
-
171
-* Customizable init-db. Personally I think template mechanism
172
- is good enough. Otherwise, maybe add hooks/post-init-db.
173
-
174
-* Make sure we do reasonable thing on binary files even in
175
- cherry-pick and rebase [DONE].
176
-
177
-* Binary diff detection fails if locale set to non English; even
178
- GNU diff 2.8.1 and 2.8.7 in C locale say different things. At
179
- least run diff under C locale (setenv LANG=C LC_ALL=C) for
180
- 1.0. It might be better to have our own binary detection
181
- logic, or even our own diff output without forking an external
182
- diff. [The former _might_ make sense for 1.0, but the latter
183
- is post 1.0].
184
-
132
133
Technical (trivial)
134
-------------------
135
189
-* Stop installing the old-name symlinks [DONE].
190
-
191
-* 'git merge-projects'?
192
-
193
- Subject: Re: Merges without bases
194
- References: <1125004228.4110.20.camel@localhost.localdomain>
195
- Date: Thu, 25 Aug 2005 15:26:36 -0700
196
- Message-ID: <7vvf1tps9v.fsf@assigned-by-dhcp.cox.net>
197
-
198
-* 'git lost-and-found'? Link dangling commits found by
199
- fsck-objects under $GIT_DIR/refs/lost-found/. Then
200
- show-branch or gitk can be used to find any lost commit.
201
- [DONE]
202
-
203
- Do not name it /lost+found/; that would probably confuse
204
- things that mistake it a mount point (not our code but
205
- somebody else's).
206
-
207
-* Add simple globbing rules to git-show-branch so that I can
208
- say 'git show-branch --heads "ko-*"' (ko-master, ko-pu, and
209
- ko-rc are in refs/tags/).
210
-
136
* We would want test scripts for the relative directory path
137
stuff Linus has been working on. Most of the C-level
138
commands should be usable with relative directory paths.