git/TODO

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
-------------

* parse-remote.sh has POSIXLY incorrect shell construct.

Message-ID: <20070505080313.GA12170@gondor.apana.org.au>

* Look into HPA's D-F conflict during rebase.

Message-ID: <463FCD7C.4020009@zytor.com>

This was resolved for git-apply codepath, but I suspect that
there are breakages in merge-recursive this exposes.

Message-ID: <7vps569904.fsf@assigned-by-dhcp.cox.net>

* Use 'git diff' not 'git diff-tree' in merge and rebase

From: James Bowes <jbowes@dangerouslyinc.com>
Message-ID: <1178398134288-git-send-email-jbowes@dangerouslyinc.com>

* gitk --left-right

From: Linus Torvalds <torvalds@linux-foundation.org>
Message-ID: <alpine.LFD.0.98.0705051524300.17381@woody.linux-foundation.org>
From: Junio C Hamano <junkio@cox.net>
Message-ID: <7vabwifl23.fsf@assigned-by-dhcp.cox.net>

* Git Hacker's Manual

From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Message-ID: <Pine.LNX.4.64.0705081709230.4167@racer.site>

* 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 <torvalds@linux-foundation.org>
Message-ID: <Pine.LNX.4.64.0704160931550.5473@woody.linux-foundation.org>

* More verbose connect to help diag & prevent boredom

From: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Message-ID: <20070506195230.GA30339@mellanox.co.il>

[jc: I think this should be done only under explicit user request to
go verbose.]

* Use blame machinery to track a single file (not path) in a finer
  grained way.

From: Linus Torvalds <torvalds@linux-foundation.org>
Message-ID: <alpine.LFD.0.98.0704201554550.9964@woody.linux-foundation.org>

[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 <junkio@cox.net>
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

* TODO list management

From: Daniel Barkalow <barkalow@iabervon.org>
Message-ID: <Pine.LNX.4.64.0704241312210.28708@iabervon.org>

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 <vagabon.xyz@gmail.com>
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 <spearce@spearce.org>
Message-ID: <20060926215745.GC8177@spearce.org>

Pasky sent an updated version to the list recently, but the
general sentiment on the list seems that existing git-fetch
has enough features to perform most of what 'mirror' does.


* AsciiDoc 8 would break our documentation.

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: limbo?]

* Delegate gitweb part to somebody else.

* Use gitattributes for more things.

 - 'precious' files that are not tracked but not
   build-products.  Currently people seem to put them in
   .gitignore, but that is not quite right, as .gitignore is
   meant for ignoring things that can be lost (build products,
   editor backup files).  "git clean -x" and "git checkout" to
   another branch that has a file where the current branch has a
   directory could lose such 'precious' files.

 - Customized "diff -p" markers per path (Johannes, on #git
   2007-04-30).

   I think it makes sense to give an extra parameter to xdiff
   machinery to affect how "diff -p" markers are constructed (as
   opposed to teach xdiff machinery to read gitattributes -- the
   code does not have path information at that level).  The
   simplest interface would be to pass a regexp and have the
   existing code always look for that regexp backwards.  A more
   complex one would involve a callback function, but I do not
   know if that kind of complexity is worth it.

 - Others???


Technical (heavier)
-------------------

* Subproject Porcelain.

 - recursive checkout
 - recursive diff


Technical (milder)
------------------

* 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.

* "git fetch" should be able to use foreign SCM import backends
  such as svnimport and cvsimport.


Technical (trivial)
-------------------

* Give --stdin to git-log, similar to git-rev-list

From: "Marco Costalba" <mcostalba@gmail.com>
Message-ID: <e5bfff550705110413q28aef3d8k3aeb0d342eeb2016@mail.gmail.com>

* Update the lockfile protocol so that closing and renaming are
  done inside lockfile commit time.  Some filesystems do not
  like an open file renamed and then closed.  Come up with a
  patch and pass Alex for an Ack.

* Mbx (not mbox) support for git-mailsplit.

* 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.

[jc: should it? -- deciding if it should may not be "trivial",
but if it turns out to be the right thing to do, the change
itself is trivial.]

* 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: