4 The latest copy of this document is found at
6 http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO
7 http://repo.or.cz/w/alt-git.git?a=blob;hb=todo;f=TODO
9 This is primarily meant for my personal reminder, but feel free
10 to pick an item from the list and work on it.
12 ----------------------------------------------------------------
17 * cherry-pick unexpected conflicts
19 From: Gerrit Pape <pape@smarden.org>
20 Subject: Re: unexpected git-cherry-pick conflict
21 Date: Wed, 13 Jun 2007 13:43:35 +0000
22 Message-ID: <20070613134336.13661.qmail@c61f4fed932273.315fe32.mid.smarden.org>
24 * 3way merge still has D/F conflict problems
26 Subject: [RFH] 3way still has D/F conflict problems...
27 Date: Mon, 23 Jul 2007 00:22:51 -0700
28 Message-ID: <7vejizmvn8.fsf@assigned-by-dhcp.cox.net>
30 I am punting on unpack-trees related D/F issues for 1.5.3. We
31 might end up rewriting read-tree after the release.
33 * Pushing into a non-bare repository more gracefully.
35 When git-push is done to a non-bare repository and updates the
36 branch that is currently checked out, we currently do not do
39 From: Linus Torvalds <torvalds@linux-foundation.org>
40 Message-ID: <Pine.LNX.4.64.0704160931550.5473@woody.linux-foundation.org>
44 From: Franck Bui-Huu <vagabon.xyz@gmail.com>
45 Message-ID: <450EABD0.1040102@innova-card.com>
47 Repeated requests against git-daemon makes it stuck under --syslog
49 [jc: does not reproduce easily for me; has anybody seen it?]
51 * Use gitattributes for more things.
53 - 'precious' files that are not tracked but not
54 build-products. Currently people seem to put them in
55 .gitignore, but that is not quite right, as .gitignore is
56 meant for ignoring things that can be lost (build products,
57 editor backup files). "git clean -x" and "git checkout" to
58 another branch that has a file where the current branch has a
59 directory could lose such 'precious' files.
67 * Subproject Porcelain.
72 From: Junio C Hamano <junkio@cox.net>
73 Message-ID: <11793556371774-git-send-email-junkio@cox.net>
75 * make merge-recursive and read-tree -u more robust when D/F
78 From: Junio C Hamano <junkio@cox.net>
79 Message-ID: <11793556371774-git-send-email-junkio@cox.net>
81 * Use blame machinery to track a single file (not path) in a finer
84 From: Linus Torvalds <torvalds@linux-foundation.org>
85 Message-ID: <alpine.LFD.0.98.0704201554550.9964@woody.linux-foundation.org>
87 [jc: I have a fixed-up one parked in 'pu' and also outlined what
88 other things I think are needed in my response:
90 Message-ID: <7vwt06wqv8.fsf@assigned-by-dhcp.cox.net>
96 * add 'tree' entries to the index.
98 From: Junio C Hamano <junkio@cox.net>
99 Message-ID: <11793556371774-git-send-email-junkio@cox.net>
101 * "pure" clones, that does not know about where it was cloned
102 from. Specifically, no [remote "origin"] in .git/config, nor
105 From: Junio C Hamano <junkio@cox.net>
106 Message-ID: <7vr6pac86g.fsf@assigned-by-dhcp.cox.net>
108 * upload-pack support to start fetching from any valid point on
109 the history, not just published refs. (Erik W. Biederman
110 <m164jc9ekx.fsf@ebiederm.dsl.xmission.com>)
112 * daemon --strict-symlink.
114 * Maybe grok PGP signed text/plain in applymbox as well.
116 * "git fetch" should be able to use foreign SCM import backends
117 such as svnimport and cvsimport.
119 * "git clone" should be a thin wrapper around init/remote/fetch/checkout
121 From: Junio C Hamano <junkio@cox.net>
122 Message-ID: <11793556371774-git-send-email-junkio@cox.net>
127 * Give --stdin to git-log, similar to git-rev-list
129 From: "Marco Costalba" <mcostalba@gmail.com>
130 Message-ID: <e5bfff550705110413q28aef3d8k3aeb0d342eeb2016@mail.gmail.com>
132 * Update the lockfile protocol so that closing and renaming are
133 done inside lockfile commit time. Some filesystems do not
134 like an open file renamed and then closed. Come up with a
135 patch and pass Alex for an Ack.
137 * Mbx (not mbox) support for git-mailsplit.
139 * git-clone fail .git/refs/foo (Yann Dirson <ydirson@altern.org>)
140 <20060610225040.GA7766@nowhere.earth>
142 * git-proxy should be spawned with sh -c 'command' $1 $2.
144 [jc: should it? -- deciding if it should may not be "trivial",
145 but if it turns out to be the right thing to do, the change
148 * Maybe a true git-proxy command that reads the first request
149 pkt-line, and redirects the request to its real destination.
151 * test scripts for the relative directory path stuff.