http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO
-What to expect until and after 1.0
-==================================
+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
if ever -- only if somebody cares enough and submits a clean
patch, perhaps ;-).
-Only handful things remain until 1.0.
-
-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.
+* tree entries in index? -- sorry, stalled
-* 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).
+* "intent to add" index entries? -- together with the above
+ needs rethinking.
-* Maybe update tutorial with a toy project that involves two or
- three developers.
+* 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).
-* Update tutorial to cover setting up repository hooks to do
- common tasks [Mostly done, with Carl's help].
-* Do we still have missing docs? If so accept patches to finish
- them.
+Technical (heavier)
+-------------------
-* Accept patches to talk about "Whoops, it broke. What's
- next?" [I think this is done].
+* 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]
-* Accept patches to make formatted tables in asciidoc to work
- well in both html and man pages (see git-diff(1)) [DONE --
- avoid them ;-)].
+* 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.
-* Work around multiple synopses lines in manual pages
- (e.g. git-bisect) [DONE -- avoid them ;-)].
+Technical (milder)
+------------------
-Technical (heavier)
--------------------
+* 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.
-* 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: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>; Post
- 1.0].
+* 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>).
-* Maybe a pack optimizer.
+* 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.
- 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.
+* 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>)
- This needs a matching smart on the dumb protocol downloader.
- [Definitely post 1.0].
+* 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>).
-* Maybe an Emacs VC backend.
+* 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>).
-* Look at libified GNU diff CVS seems to use, or libxdiff.
- [Daniel has his own diff tool almost ready to start
- integrating and testing; Post 1.0]
+* Per user .gitconfig across repositories -- ongoing.
-* Plug-in file-level merges [Post 1.0]. On the other hand, we
- may not even need this; just tell people to run "xxdiff -U" on
- the working tree files.
+* Encourage competition between annotate vs blame. Maybe come
+ up with some nontrivial test cases.
-* 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.]
+* Subprojects. Try "gitlink" -- sorry, stalled.
+* Rebase and checkout -m should be able to use recursive
+ strategy as well. These commands currently do not work across
+ renames.
-Technical (milder)
-------------------
+* 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.
+
+ <43CC695E.2020506@codeweavers.com>
-* strip leading directory from ls-tree output, to match ls-files
- output.
+* 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.
- 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.
+ <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
* 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 [can be post
- 1.0].
+ Would help internal tree-diff in rev-list as well.
-* merge-recursive needs to register conflicting paths as higher
- stage entries in the index. For that, it first needs to
- construct three trees whose paths are already renamed, and
- call 3-way read-tree. Alternatively, update-index needs to
- give it a way to construct higher stages [DONE using the
- "alternatively" implementation].
+* daemon --strict-symlink.
-* daemon --strict-symlink [can be post 1.0].
-
-* Binary package split. Plan laid out and discussion mostly
- done. [RPM side done; Debian side thrown over the wall.]
+* daemon --base-path does not apply automatically to whitelist
+ somehow feels wrong. If somebody cares enough, accept
+ patches.
* Perhaps detect cloning request in upload-pack and cache the
result for next cloning request until any of our refs change.
-* Perhaps accept patch to optionally allow '--fuzz' in
- 'git-apply'.
-
-* Allow 'git apply' to accept GNU diff 2.7 output that forgets
- to say '\No newline' if both input ends with incomplete
- lines.
-
* Maybe grok PGP signed text/plain in applymbox as well.
-* Enhance "git repack" to not always use --all; this would be
- handy if the repository contains wagging heads like "pu" in
- git.git repository.
-
-* 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)
-------------------
-* We would want test scripts for the relative directory path
- stuff Linus has been working on. Most of the C-level
- commands should be usable with relative directory paths.
+* 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.
-* 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`).
projects / git.git / blobdiff