The GIT To-Do File ================== The latest copy of this document is found at http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO http://repo.or.cz/w/alt-git.git?a=blob;hb=todo;f=TODO This is primarily meant for my personal reminder, but feel free to pick an item from the list and work on it. ---------------------------------------------------------------- Recent issues ------------- * Handling pushing into non-bare repository more gracefully. When git-push is done to a non-bare repository and updates the branch that is currently checked out, we currently do not do anything special. From: Linus Torvalds Message-ID: * Use blame machinery to track a single file (not path) in finer grained way. From: Linus Torvalds Message-ID: [jc: I have a fixed-up one parked in 'pu' and also outlined what other things I think are needed in my response: Message-ID: <7vwt06wqv8.fsf@assigned-by-dhcp.cox.net> ] * Use git.git as the first public guinea pig of subproject From: Junio C Hamano Message-ID: <7vmz13z4au.fsf@assigned-by-dhcp.cox.net> Use git.git as the first public guinea pig of subproject stuff, by dropping git-gui/ directory first and then binding git-gui.git as a subproject there. This needs to wait at least until v1.5.2 ships and gets installed at kernel.org and repo.or.cz * Decide what to do with 'filter' and 'ident' attribute patches. From: Linus Torvalds Message-ID: If we were to include it, we would need to make it clear that this is a long piece of rope and you can strangle yourself with it unless you are careful, and clarify what is and isn't considered to be "careful". I have parked updates in 'pu', but I do not know they are clear enough. * TODO list management From: Daniel Barkalow Message-ID: Maybe abandon this and have something similar on the main branch, starting full at the beginning of the cycle and ending empty (or full of "not in next release" entries) at the release? * git-daemon bug? From: Franck Bui-Huu Message-ID: <450EABD0.1040102@innova-card.com> Repeated requests against git-daemon makes it stuck under --syslog [jc: does not reproduce easily for me; has anybody seen it?] * git-mirror (reverse of git-push --all). From: Shawn Pearce Message-ID: <20060926215745.GC8177@spearce.org> [jc: may want the finished version for inclusion] * AsciiDoc 8 would break our documentation. From: Stefan Richter Message-ID: <4523EC14.6070806@s5r6.in-berlin.de> AsciiDoc 8 does not grok documents written for AsciiDoc 7 out of the box. [jc: limbo?] * Gitweb diff on merge commits From: Linus Torvalds Subject: Re: git show and gitweb gives different result for kernel Message-ID: Maybe allow gitweb to show diff with any parent and diff --cc, not just diff with the first parent for a merge. [jc: Jakub is interested in it] Technical (milder) ------------------ * upload-pack support for start fetching from any valid point on the history, not just published refs. (Erik W. Biederman ) * daemon --strict-symlink. * Maybe grok PGP signed text/plain in applymbox as well. * "git fetch" should be able to use foreign SCM import backends such as svnimport and cvsimport. Technical (trivial) ------------------- * Mbx (not mbox) support for git-mailsplit. * git-clone fail .git/refs/foo (Yann Dirson ) <20060610225040.GA7766@nowhere.earth> * git-proxy should be spawned with sh -c 'command' $1 $2. [jc: should it?] * Maybe a true git-proxy command that reads the first request pkt-line, and redirects the request to its real destination. * test scripts for the relative directory path stuff. Local Variables: mode: text End: