git/TODO

111 lines
2.9 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

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
Recent issues
-------------
From: A Large Angry SCM <gitzilla@gmail.com>
Subject: Notes on Using Git with Subprojects
Message-ID: <45196628.9010107@gmail.com>
[jc: a very nice write-up of a subprojects workflow. I do not
remember if it produced any actionable items, though]
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
Message-ID: <450EABD0.1040102@innova-card.com>
Repeated requests against git-daemon makes it stuck
[jc: does not reproduce easily for me; has anybody seen it?]
From: Shawn Pearce <spearce@spearce.org>
Message-ID: <20060926215745.GC8177@spearce.org>
git-mirror (reverse of git-push --all).
[jc: any progress?]
From: Junio C Hamano <junkio@cox.net>
Message-ID: <7v7izrzpk2.fsf@assigned-by-dhcp.cox.net>
Deal with rfc2822-invalid author mail address in send-email.
[jc: forgot to apply?]
From: Nicolas Pitre <nico@cam.org>
Subject: [PATCH 8/6] let the GIT native protocol use offsets to delta base when
[jc: applied all but I suspect git-push side hasn't been converted?]
From: Shawn Pearce <spearce@spearce.org>
Message-ID: <20060930045037.GB18479@spearce.org>
"git ref-log" command to interact with ref-log?
[jc: not much interest from users?]
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Message-ID: <4523EC14.6070806@s5r6.in-berlin.de>
AsciiDoc 8 does not grok documents written for AsciiDoc 7 out of
the box.
[jc: status?]
From: Josh Triplett <josh@freedesktop.org>
Message-ID: <451A30E4.50801@freedesktop.org>
git-split
[jc: no response to the initial review comments]
Technical (milder)
------------------
* duplicated refspec given to "fetch-pack a a a" makes it emit
strange error message because it triggers the "match only
once" logic. Maybe strip the dups on the input side
(Uwe Zeisberger
<20060608073857.GA5072@informatik.uni-freiburg.de>).
* map only parts of huge packfiles and LRU fragments of them.
People are starting to try git on projects with deep history
and/or many objects, e.g. Mozilla.
* upload-pack support for start fetching from any valid point on
the history, not just published refs. (Erik W. Biederman
<m164jc9ekx.fsf@ebiederm.dsl.xmission.com>)
* daemon --strict-symlink.
* Maybe grok PGP signed text/plain in applymbox as well.
Technical (trivial)
-------------------
* Mbx (not mbox) support for git-mailsplit.
* log-tree.c: pad sequence numbers with leading 0 if a series is
larger than 9, around ll.133?
* git-clone fail .git/refs/foo (Yann Dirson <ydirson@altern.org>)
<20060610225040.GA7766@nowhere.earth>
* git-proxy should be spawned with sh -c 'command' $1 $2.
* 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: