2005-12-21 TODO updates.
Junio C Hamano committed
Dec 21, 2005 at 22:41 UTC
bd8b47db1a26557181fe4e807dd282b96863b3e6
1 file changed
+40
-49
TODO
+40
-49
@@ -6,8 +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
-What to expect until and after 1.0
10
-==================================
9
+What to expect from now on
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
@@ -16,16 +16,10 @@ 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
-
19
20
Documentation
21
-------------
22
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.
28
-
23
* Talk about using rsync just once at the beginning when
24
initializing a remote repository so that local packs do not
25
need to be expanded. I personally do not think we need tool
@@ -34,21 +28,24 @@ Documentation
28
* Maybe update tutorial with a toy project that involves two or
29
three developers.
30
37
-* Update tutorial to cover setting up repository hooks to do
38
- common tasks [Mostly done, with Carl's help].
31
40
-* Do we still have missing docs? If so accept patches to finish
41
- them.
32
+Design issues
33
+-------------
34
+
35
+* Plug-in file-level merges. On the other hand, we may not even
36
+ need this; just tell people to run "xxdiff -U" on the working
37
+ tree files.
38
43
-* Accept patches to talk about "Whoops, it broke. What's
44
- next?" [I think this is done].
39
+* Ref namespace management. Perhaps use refs/local/ suggestion
40
+ by Linus. [Does not seem to be high on people's priority list,
41
+ and not interested myself. People can resurrect this
42
+ discussion if they want.]
43
46
-* Accept patches to make formatted tables in asciidoc to work
47
- well in both html and man pages (see git-diff(1)) [DONE --
48
- avoid them ;-)].
44
+* Perhaps "everything in config file"? Especially remotes/
45
+ shortcuts. I am modestly negative about this.
46
50
-* Work around multiple synopses lines in manual pages
51
- (e.g. git-bisect) [DONE -- avoid them ;-)].
47
+* Perhaps "setting umask from git_config()"? I am modestly
48
+ negative about this.
49
50
51
Technical (heavier)
@@ -57,8 +54,7 @@ Technical (heavier)
54
* Libification. There are many places "run once" mentality is
55
ingrained in the management of basic data structures, which
56
need to be fixed. [Matthias Urlichs is already working on
60
- this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>; Post
61
- 1.0].
57
+ this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>]
58
59
* Maybe a pack optimizer.
60
@@ -71,27 +67,28 @@ Technical (heavier)
67
releases.
68
69
This needs a matching smart on the dumb protocol downloader.
74
- [Definitely post 1.0].
70
71
* Maybe an Emacs VC backend.
72
73
* Look at libified GNU diff CVS seems to use, or libxdiff.
74
[Daniel has his own diff tool almost ready to start
80
- integrating and testing; Post 1.0]
81
-
82
-* Plug-in file-level merges [Post 1.0]. On the other hand, we
83
- may not even need this; just tell people to run "xxdiff -U" on
84
- the working tree files.
85
-
86
-* Ref namespace management. Perhaps use refs/local/ suggestion
87
- by Linus. [Does not seem to be high on people's priority list,
88
- and not interested myself. People can resurrect this
89
- discussion if they want.]
75
+ integrating and testing]
76
77
78
Technical (milder)
79
------------------
80
81
+* send-pack/receive-pack protocol updates, to allow the receiver
82
+ to report what it did to the ref update requests.
83
+
84
+* Perhaps a smarter HTTP anonymous download via CGI.
85
+
86
+* Prepare to enable "always use symbolic refs for HEAD" patch.
87
+ We need a timeline to force Porcelains to get ready.
88
+
89
+* Forbid/ignore pack names that do not conform to the convention
90
+ sha1_pack_name() assumes and reject in check_packed_git_idx().
91
+
92
* strip leading directory from ls-tree output, to match ls-files
93
output.
94
@@ -102,20 +99,9 @@ Technical (milder)
99
100
* diff stopping at the first output; qgit wants to know if this
101
tree has any A or D from the other tree and nothing else.
105
- Would help internal tree-diff in rev-list as well [can be post
106
- 1.0].
102
+ Would help internal tree-diff in rev-list as well.
103
108
-* merge-recursive needs to register conflicting paths as higher
109
- stage entries in the index. For that, it first needs to
110
- construct three trees whose paths are already renamed, and
111
- call 3-way read-tree. Alternatively, update-index needs to
112
- give it a way to construct higher stages [DONE using the
113
- "alternatively" implementation].
114
-
115
-* daemon --strict-symlink [can be post 1.0].
116
-
117
-* Binary package split. Plan laid out and discussion mostly
118
- done. [RPM side done; Debian side thrown over the wall.]
104
+* daemon --strict-symlink.
105
106
* Perhaps detect cloning request in upload-pack and cache the
107
result for next cloning request until any of our refs change.
@@ -127,11 +113,10 @@ Technical (milder)
113
to say '\No newline' if both input ends with incomplete
114
lines.
115
130
-* Maybe grok PGP signed text/plain in applymbox as well.
116
+* Perhaps deal with "Files differ" (binary diff) in non C
117
+ locales.
118
132
-* Enhance "git repack" to not always use --all; this would be
133
- handy if the repository contains wagging heads like "pu" in
134
- git.git repository.
119
+* Maybe grok PGP signed text/plain in applymbox as well.
120
121
* Output full path in the "git-rev-list --objects" output, not
122
just the basename, and see the improved clustering results in
@@ -141,6 +126,12 @@ Technical (milder)
126
Technical (trivial)
127
-------------------
128
129
+* Versioning scheme. The next maintenance installment will be
130
+ 1.0.3 not 1.0.0c. The next feature release would be 1.1.0.
131
+
132
+* Either drop supporting Debian myself or coerce patches out of
133
+ the official maintainer.
134
+
135
* We would want test scripts for the relative directory path
136
stuff Linus has been working on. Most of the C-level
137
commands should be usable with relative directory paths.