TODO update
Junio C Hamano committed
Feb 13, 2007 at 15:47 UTC
f3f63cf475c77425b1b21a773d85323554a334cb
1 file changed
+5
-39
TODO
+5
-39
@@ -9,23 +9,9 @@ The GIT To-Do File
9
Recent issues
10
-------------
11
12
-From: Karl Hasselström <kha@treskal.com>
13
-Message-ID: <20061026172603.GA21256@diana.vm.bytemark.co.uk>
14
-
15
-It might make sense to make --use-separate-remote the default.
16
-
17
-[jc: The only downside that I can think of is that it affects me
18
-or anybody who works on more than one machine on multiple
19
-branches slightly negatively.
20
-
21
-But that is just a minor inconvenience to a minority. Most of
22
-the world follow others' repositories, and defaulting to use
23
-separate-remotes would help them a lot.]
24
-
25
-From: Junio C Hamano <junkio@cox.net>
26
-
27
-commit walkers still have issues with packed and then pruned
28
-refs.
12
+Maybe abandon this and have something similar on the main
13
+branch, starting full at the beginning of the cycle and ending
14
+empty (or full of "not in next release" entries) at the release?
15
16
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
17
Message-ID: <450EABD0.1040102@innova-card.com>
@@ -41,13 +27,6 @@ git-mirror (reverse of git-push --all).
27
28
[jc: may want the finished version for inclusion]
29
44
-From: Shawn Pearce <spearce@spearce.org>
45
-Message-ID: <20060930045037.GB18479@spearce.org>
46
-
47
-"git ref-log" command to interact with ref-log?
48
-
49
-[jc: not much interest from users?]
50
-
30
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
31
Message-ID: <4523EC14.6070806@s5r6.in-berlin.de>
32
@@ -68,18 +47,6 @@ not just diff with the first parent for a merge.
47
Technical (milder)
48
------------------
49
71
-* duplicated refspec given to "fetch-pack a a a" makes it emit
72
- strange error message because it triggers the "match only
73
- once" logic. Maybe strip the dups on the input side
74
- (Uwe Zeisberger
75
- <20060608073857.GA5072@informatik.uni-freiburg.de>).
76
-
77
-* map only parts of huge packfiles and LRU fragments of them.
78
- People are starting to try git on projects with deep history
79
- and/or many objects, e.g. Mozilla.
80
-
81
- [jc: ping Shawn or give up and do this myself.]
82
-
50
* upload-pack support for start fetching from any valid point on
51
the history, not just published refs. (Erik W. Biederman
52
<m164jc9ekx.fsf@ebiederm.dsl.xmission.com>)
@@ -93,14 +60,13 @@ Technical (trivial)
60
61
* Mbx (not mbox) support for git-mailsplit.
62
96
-* log-tree.c: pad sequence numbers with leading 0 if a series is
97
- larger than 9, around ll.133?
98
-
63
* git-clone fail .git/refs/foo (Yann Dirson <ydirson@altern.org>)
64
<20060610225040.GA7766@nowhere.earth>
65
66
* git-proxy should be spawned with sh -c 'command' $1 $2.
67
68
+[jc: should it?]
69
+
70
* Maybe a true git-proxy command that reads the first request
71
pkt-line, and redirects the request to its real destination.
72