X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=4135038fb326afa1e3568487ff680b2066e56927;hb=4ec53b6fb6f7454e45a561d6a62fd4e45e0cd2e9;hp=04a4d17d46882d9c791d5e988f410e5d79842f41;hpb=c8a7baf32daa649e69662e1197fe8884e0cd0f92;p=git.git diff --git a/TODO b/TODO index 04a4d17d..4135038f 100644 --- a/TODO +++ b/TODO @@ -1,145 +1,151 @@ -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 ------------- -* 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.. + three developers. + + +Design issues +------------- -* Update tutorial to cover setting up repository hooks to do - common tasks. +* 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. -* Accept patches to finish missing docs. +* Ref namespace management. Perhaps use refs/local/ suggestion + by Linus. [Does not seem to be high on people's priority list, + and not interested myself. People can resurrect this + discussion if they want.] + +* Perhaps "everything in config file"? Especially remotes/ + shortcuts. I am modestly negative about this. 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.] - -* 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. - -* 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. - -* 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. +* Libification. There are many places "run once" mentality is + ingrained in the management of basic data structures, which + need to be fixed. [Matthias Urlichs is already working on + this: ] + +* Maybe a pack optimizer. + + Given a set of objects and a set of refs (probably a handful + branch heads and point release tags), find a set of packs to + allow reasonably minimum download for all of these classes of + people: (1) somebody cloning the repository from scratch, (2) + somebody who tends to follow the master branch head reasonably + closely, (3) somebody who tends to follow only the point + releases. + + This needs a matching smart on the dumb protocol downloader. * Maybe an Emacs VC backend. +* Look at libified GNU diff CVS seems to use, or libxdiff. + [Daniel has his own diff tool almost ready to start + integrating and testing] + Technical (milder) ------------------ -* Tool renames [STARTED]. +* send-pack/receive-pack protocol updates, to allow the receiver + to report what it did to the ref update requests. -* Have Daniel's read-tree graduate from "pu" after plugging leaks. +* Perhaps a smarter HTTP anonymous download via CGI. -* Implement a merge backend using Daniel's read-tree. +* Prepare to enable "always use symbolic refs for HEAD" patch. + We need a timeline to force Porcelains to get ready. Last + time I looked at them I got an impression that gitweb was not + ready. -* 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. +* Forbid/ignore pack names that do not conform to the convention + sha1_pack_name() assumes and reject in check_packed_git_idx() + [In pu] -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* strip leading directory from ls-tree output, to match ls-files + output. -* Bug Martin for archimport script documentation. + I am of two minds about this one. diff output must always be + -p1 format no matter where the command was started, and + ls-tree might be easier to use if it matched diff, not + ls-files. -* More portability. I dropped a SunOS patch on the floor by - somebody. + [We should not do this, or do this carefully, if we were to + merge the "git-checkout (--|) work from + subdirectory" patch.] -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty. +* Any Porcelain-ish we forgot or punted to make usable from + subdirectory? I think the last pass caught everything and + what are remaining are whole-tree or whole repository + operations. -* Perhaps accept patches to introduce the concept of "patch flow - expressed as ref mappings" Josef has been advocating about. +* 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. -* Perhaps accept patches to do undo/redo. +* daemon --strict-symlink. -* Maybe grok PGP signed text/plain in applymbox as well. +* Perhaps detect cloning request in upload-pack and cache the + result for next cloning request until any of our refs change. -* 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. +* Perhaps accept patch to optionally allow '--fuzz' in + 'git-apply'. -* A tool to detect, show and prune already merged topic - branches. +* Allow 'git apply' to accept GNU diff 2.7 output that forgets + to say '\No newline' if both input ends with incomplete + lines. -* Enhance "git repack" to not always use --all; this would be - handy if the repository contains wagging heads like "pu" in - git.git repository. +* Perhaps deal with "Files differ" (binary diff) in non C + locales. -* 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. +* Maybe grok PGP signed text/plain in applymbox as well. -* Option to limit rename detection for more than N paths. +* Output full path in the "git-rev-list --objects" output, not + just the basename, and see the improved clustering results in + better packing [Tried, but did not work out well]. Technical (trivial) ------------------- -* Perhaps "git branch -d" to delete a branch. +* Versioning scheme. The next maintenance installment will be + 1.0.3 not 1.0.0c. The next feature release would be 1.1.0. + +* Either drop supporting Debian myself or coerce patches out of + the official maintainer. * 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: - - update-cache - ls-files - diff-files - diff-cache - diff-tree - rev-list - rev-parse - -* In a freashly created empty repository, `git fetch foo:bar` + stuff Linus has been working on. Most of the C-level + commands should be usable with relative directory paths. + +* In a freshly created empty repository, `git fetch foo:bar` works OK, but `git checkout bar` afterwards does not (missing `.git/HEAD`).