X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=4135038fb326afa1e3568487ff680b2066e56927;hb=f6cd1a71265b2e022ecddbcbe98d4f6374b6df42;hp=488d384ff84397c7ff1fcaeff17dc1a2c9d71990;hpb=788c7002ac87a334cf4286eb10f7c7e05a645aae;p=git.git diff --git a/TODO b/TODO index 488d384f..4135038f 100644 --- a/TODO +++ b/TODO @@ -1,151 +1,153 @@ -What to expect after 0.99.5 -=========================== +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. - -* Link howto docs from the git.txt page. [DONE] - -* Update the SubmittingPatches document to add MUA specific - hints on how to disable unwanted MIME and flowed-text by - collecting past list postings. Accept patches from people who - was hit by shiny blue bat to update the same. [NEEDSWORK] - * 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. + support for this (but see below about optimized cloning). + +* Maybe update tutorial with a toy project that involves two or + three developers. -* Update tutorial to cover shared repository style a bit more, - maybe with a toy project that involves two or three - repositories. -* Update tutorial to cover setting up repository hooks to do - common tasks. [IN PROGRESS] +Design issues +------------- + +* 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. -* Get help to properly use asciidoc in tutorial. +* 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.] -* Maybe justify and demonstrate an Octopus in the tutorial. Add - it to the glossary. +* 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. - [Underway. Thanks Daniel and Fredrik for taking an - initiative.] +* 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: ] -* 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. + 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. -Technical (milder) ------------------- + This needs a matching smart on the dumb protocol downloader. -* When the branch head pointed by $GIT_DIR/HEAD changes while - the index file and working tree are looking the other way - (e.g. somebody pushed into your repository, or you ran "git - fetch" to update the ref your working tree is on), "git - checkout" without -f gets confused. Figure out a good way to - handle this. [DONE] +* Maybe an Emacs VC backend. - We still have the same issue with "git fetch". Fetching into - the branch one is on _may_ need to do the same thing as - fetching into anonymous head and then do the resolve. At - least it needs a warning. [NEEDSWORK] +* Look at libified GNU diff CVS seems to use, or libxdiff. + [Daniel has his own diff tool almost ready to start + integrating and testing] -* "git commit -m" should work for initial commits and perhaps - merge commits as well. Warning about merge is still a good - thing to do, while -m is useful in scripted non-interactive - use, so we need to be careful. [DONE - waiting for response] -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +Technical (milder) +------------------ -* Bug Ryan and work with him to update send-email easier to use. - [Resurrected it for Debian build.] +* send-pack/receive-pack protocol updates, to allow the receiver + to report what it did to the ref update requests. -* Look at portability fixes from Jason Riedy +* Perhaps a smarter HTTP anonymous download via CGI. - http://www.cs.berkeley.edu/~ejr/gits/git.git#portable +* 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. - [Looked at it. Maybe promising. Maybe not.] +* Forbid/ignore pack names that do not conform to the convention + sha1_pack_name() assumes and reject in check_packed_git_idx() + [In pu] -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty. +* strip leading directory from ls-tree output, to match ls-files + output. -* Perhaps accept patches to introduce the concept of "patch flow - expressed as ref mappings" Josef has been advocating about. + 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. -* Perhaps accept patches to do undo/redo. + [We should not do this, or do this carefully, if we were to + merge the "git-checkout (--|) work from + subdirectory" patch.] -* MIMEified applymbox to grok B and Q encodings in headers and - turn them into UTF-8; unwrap QP; explode multipart. +* 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. -* "git cherry-pick" that applies the patch an existing commit - introduces in its ancestry chain, possibly using the 3-way - merge machinery. [Done. Needs documentation.] +* 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. -* Update rebase using the cherry-pick command. [Done] +* daemon --strict-symlink. -* Redo "git revert" using 3-way merge machinery. [Done] +* Perhaps detect cloning request in upload-pack and cache the + result for next cloning request until any of our refs change. -* A tool to detect, show and prune already merged topic - branches. +* Perhaps accept patch to optionally allow '--fuzz' in + 'git-apply'. -* Set up an automated documentation rebuilding procedure at - kernel.org, using update hook mechanism. [Almost, but not - quite.] Describe it in a howto form [Done]. +* 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. -* Add names to all nodes in show-branch. +* 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) ------------------- -* Look at and merge Debian fixes from Tommi [Done]. +* Versioning scheme. The next maintenance installment will be + 1.0.3 not 1.0.0c. The next feature release would be 1.1.0. -* Perhaps "git branch -d" to delete a branch. - -* Remove "git clone-dumb-http". +* 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 + 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`). Local Variables: