-What to expect after 0.99.6
-===========================
+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
+
+
+What to expect from now on
+==========================
This is written in a form of to-do list for me, so if I say
"accept patch", it means I do not currently plan to do that
myself. People interested in seeing it materialize please take
-a hint.
+a hint. Also whatever I marked "Perhaps" do not have to happen
+if ever -- only if somebody cares enough and submits a clean
+patch, perhaps ;-).
-Documentation
+Design issues
-------------
-* Accept patches from people who actually have done CVS
- migration and update the cvs-migration documentation.
- Link the documentation from the main git.txt page.
-
-* Accept patches from people who were hit by shiny blue bat to
- update the SubmittingPatches [ONGOING].
-
-* Talk about using rsync just once at the beginning when
- initializing a remote repository so that local packs do not
- need to be expanded. I personally do not think we need tool
- support for this (but see below about optimized cloning).
-
-* Maybe update tutorial with a toy project that involves two or
- three developers..
+* tree entries in index? -- sorry, stalled
-* Update tutorial to cover setting up repository hooks to do
- common tasks.
+* "intent to add" index entries? -- together with the above
+ needs rethinking.
-* Accept patches to finish missing docs.
+* Plug-in file-level merges. On the other hand, we may not even
+ need this; just tell people to run "xxdiff -U" on the working
+ tree files (or kompare).
Technical (heavier)
-------------------
-* Tony Luck reported an unfortunate glitch in the 3-way merge.
- Encourage discussions to come up with a not-so-expensive way
- to catch the kind of ambiguities that led to his misery.
- [Daniel's patch looks quite promising, so is the one from
- Fredrik.]
+* Libification. There are many places "run once" mentality is
+ ingrained in the management of basic data structures, which
+ need to be fixed. [Matthias Urlichs was already working on
+ this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>, but I
+ do not know what happened to his efforts]
-* HPA has two projects, klibc and klibc-kbuild, that have large
- set of overlapping files in different paths (i.e. one has many
- renames from the other). There currently is no way for git to
- help keep these two trees in sync, merging criss-cross between
- them. The merge logic should be able to take advantage of
- rename/copy detection smarts git-diff-* family has. Linus,
- me, and Daniel outlined a smarter merge strategy for this.
- Try them out.
+* Lazy clones that can be controlled by the user, ranging from
+ totally on-demand a la CVS/SVN to "cache down to this old
+ commit so that I can make full use of git on at least recent
+ history". This need a lot of work in making tools to exit
+ gracefully when they hit unavailable objects while offline.
-* To make it easier to experiment with different merge
- strategies, make git-merge driver that will run merge backends
- for the best merge [Outlined the idea; just do it].
-* We might want to optimize cloning with GIT native transport
- not to explode the pack, and store it in objects/pack instead.
- We would need a tool to generate an idx file out of a pack
- file for this. Also this itself may turn out to be a bad
- idea, making the set of packs in repositories everybody has
- different from each other.
+Technical (milder)
+------------------
-* Maybe a pack optimizer. I am not convinced that packing all
- objects into a single pack and removing all the existing panck
- is the right way to go, since that would work against people
- who already have those packs.
+* git grep should be able to omit prefix when invoked from a
+ subdirectory. Either make it an option or default with
+ --full-name like ls-files does.
-* Maybe an Emacs VC backend.
+* 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.
-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>)
-* Tool renames [STARTED].
+* git-daemon side support for virtual hosting. Client side
+ is ready in 1.4.0 (Jon Loeliger <1149610100.23938.75.camel@cashmere.sps.mot.com>).
-* Have Daniel's read-tree graduate from "pu" after plugging leaks.
+* teach git-upload-pack not to ack-continue early when the
+ client has roots it does not know about but it already has
+ learned the fork points for all the requested heads
+ (Ralf Baechle <20060524131022.GA11449@linux-mips.org>).
-* Implement a merge backend using Daniel's read-tree.
+* Per user .gitconfig across repositories -- ongoing.
-* Accept Fredrik merge after renaming it (I want to name the
- driver 'git merge'). Suggest where to place *.py stuff --
- probably in $(share)/git-core/ and add Makefile entry for
- installation.
+* Encourage competition between annotate vs blame. Maybe come
+ up with some nontrivial test cases.
-* Encourage concrete proposals to commit log message templates
- we discussed some time ago.
+* Subprojects. Try "gitlink" -- sorry, stalled.
-* Bug Martin for archimport script documentation.
+* Rebase and checkout -m should be able to use recursive
+ strategy as well. These commands currently do not work across
+ renames.
-* More portability. I dropped a SunOS patch on the floor by
- somebody.
+* Decide what to do about rebase applied to merged head. One
+ extreme is to allow rebase if "rev-list ours..theirs" gives
+ anything. This loosens the current merge-base based approach.
+ The other extreme is to refuse rebase if "rev-list
+ theirs..ours" contains any merge commit, which was discussed
+ on the list.
-* Accept patches to cause "read-tree -u" delete a directory when
- it makes it empty.
+ <43CC695E.2020506@codeweavers.com>
-* Perhaps accept patches to introduce the concept of "patch flow
- expressed as ref mappings" Josef has been advocating about.
+* Decide what the right thing to do upon an empty merge commit,
+ when both branches happen to have obtained the same set of
+ changes through different history. Not recording such keeps
+ the history simpler, and the next merge would soon create a
+ true merge commit anyway, but this does not feel quite right.
-* Perhaps accept patches to do undo/redo.
+ <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
-* Maybe grok PGP signed text/plain in applymbox as well.
-
-* Perhaps a tool to revert a single file to pre-modification
- state? git-cat-file blob `git-ls-files | grep foo` >foo or
- git-cat-file blob `git-ls-tree HEAD foo` >foo? What should
- the command be called? git-revert is taken so is
- git-checkout.
+* diff stopping at the first output; qgit wants to know if this
+ tree has any A or D from the other tree and nothing else.
+ Would help internal tree-diff in rev-list as well.
-* A tool to detect, show and prune already merged topic
- branches.
+* daemon --strict-symlink.
-* Enhance "git repack" to not always use --all; this would be
- handy if the repository contains wagging heads like "pu" in
- git.git repository.
+* daemon --base-path does not apply automatically to whitelist
+ somehow feels wrong. If somebody cares enough, accept
+ patches.
-* Internally split the project into non-doc and doc parts; add
- an extra root for the doc part and merge from it; move the
- internal doc source to a separate repository, like the +Meta
- repository; experiment if this results in a reasonable
- workflow, and document it in howto form if it does.
+* Perhaps detect cloning request in upload-pack and cache the
+ result for next cloning request until any of our refs change.
-* Option to limit rename detection for more than N paths.
+* Maybe grok PGP signed text/plain in applymbox as well.
Technical (trivial)
-------------------
-* Perhaps "git branch -d" to delete a branch.
+* git-proxy should be spawned with sh -c 'command' $1 $2.
-* We would want test scripts for the relative directory path
- stuff Linus has been working on. So far, the following
- commands should be usable with relative directory paths:
+* Maybe a true git-proxy command that reads the first request
+ pkt-line, and redirects the request to its real destination.
- update-cache
- ls-files
- diff-files
- diff-cache
- diff-tree
- rev-list
- rev-parse
+* test scripts for the relative directory path stuff.
-* In a freashly created empty repository, `git fetch foo:bar`
+* In a freshly created empty repository, `git fetch foo:bar`
works OK, but `git checkout bar` afterwards does not (missing
`.git/HEAD`).