http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO
-Tool Renames Plan
-=================
-
- - Immedately after 0.99.9, the backward compatible symbolic
- links in $(bindir) will be removed [DONE].
-
- git-ssh-push and git-ssh-pull pair is not going away if ever.
- Each of these old-name commands continues to invoke its
- old-name counterpart on the other end.
-
- - There was a discussion to move bulk of the git-* programs out
- of /usr/bin and use /usr/lib/git; the central mechanism was
- done, but the actual move is postponed post 1.0.
-
-
-What to expect after 0.99.9
-===========================
+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
Documentation
-------------
-* Help Jon Loeliger to find place in the documentation to place
- his drawing [DONE].
+* No pending issues at the moment. "Revamp Tutorial" initiative
+ by Bruce Fields ongoing and things are looking better.
+
+
+Design issues
+-------------
+
+* Rehash "git commit" with various parameters to be more
+ intuitive without breaking traditinal users too much. We need
+ to phase this in, especially if we are going to change "git
+ commit" to imply the current "git commit -a" behaviour.
-* 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.
+* "intent to add" index entries.
-* 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).
+* 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.
-* Maybe update tutorial with a toy project that involves two or
- three developers.
+* Doing a merge in a separate directory.
-* Update tutorial to cover setting up repository hooks to do
- common tasks.
+* Make 'format-patch' take revision limiters similar to
+ rev-list. For example:
-* Do we still have missing docs? If so accept patches to finish
- them.
+ A C
+ ....---x---o---o---x---o---o
+ /
+ /
+ /
+ ....---x---o---o
+ B
-* Accept patches to talk about "Whoops, it broke. What's
- next?" [Started].
+ we should be able to format commits 'o', without duplicates,
+ by:
-* Accept patches to make formatted tables in asciidoc to work
- well in both html and man pages (see git-diff(1)).
+ $ git format-patch ^A ^B C
+ Currently the closest approximation is
-Technical (heavier)
--------------------
+ $ git format-patch A..C B..C
-* Assess the side effects of "make the rest of the things
- magically work from any subdirectory" change by Linus. It is
- a good change in principle and we would like to have that
- behaviour but some tool implementations I am sure are assuming
- to never run from anywhere other than the top. [Post 1.0]
+ which results in the last two commits including C formatted
+ twice.
-* Ref namespace management. Perhaps use refs/local/ suggestion
- by Linus.
-* Git daemon, when deployed at kernel.org, might turn out to be
- quite a burden, since it needs to generate customized packs
- every time a new request comes in. It may be worthwhile to
- precompute some packs for popular sets of heads downloaders
- have and serve that, even if that could give more than the
- client asks for in some cases. We will know about this soon
- enough [DONE part to allow using precomputed pack, but not
- dynamic caching part].
+Technical (heavier)
+-------------------
* 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].
+ this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>]
* Maybe a pack optimizer.
closely, (3) somebody who tends to follow only the point
releases.
-* Maybe an Emacs VC backend.
+ This needs a matching smart on the dumb protocol downloader.
-* 'git split-projects'? This requires updated 'git-rev-list' to
- skip irrelevant commits.
- Message-ID: <Pine.LNX.4.63.0509221617300.23242@iabervon.org>
+* 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; Post 1.0]
-
-* Plug-in file-level merges [Post 1.0].
+ integrating and testing]
Technical (milder)
------------------
-* Binary package split. Plan laid out and discussion mostly
- done. [RPM side done; Debian side delegated]
+* Subprojects. I think the "bind commit" approach has been
+ outlined at sufficiently detailed level. Maybe find time to
+ actually start prototyping it?
-* User-relative paths by Andreas Ericsson. [Need to ping]
+ <7vacdzkww3.fsf@assigned-by-dhcp.cox.net>
-* Proxing git:// connection by Paul Collins. [Need to ping]
+* Shallow clones.
-* Maybe look at Cogito and see if I can help Pasky to adjust to
- the later core features?
+* Mark entries as "assume unchanged" in the index.
+ New option to update-index to set or drop the bit is needed.
-* Perhaps detect cloning request in upload-pack and cache the
- result for next cloning request until any of our refs change.
+ - update-index --no-stat paths...
+ - update-index --with-stat paths...
-* Encourage concrete proposals to commit log message templates
- we discussed some time ago.
+ Also a config item '[core] trust_stat = false' would enable
+ this automatically:
-* Perhaps accept patches to do undo/redo.
+ - "update-index" with or without --add would mark the path
+ after registering. Should we make the working tree file
+ read-only at this point?
-* Perhaps accept patch to optionally allow '--fuzz' in
- 'git-apply'.
+ - checkout-index -u would mark the path and makes the working
+ tree file read-only.
-* Allow 'git apply' to accept GNU diff 2.7 output that forgets
- to say '\No newline' if both input ends with incomplete
- lines.
+ Impacts to various commands:
-* Maybe grok PGP signed text/plain in applymbox as well.
+ - update-index --refresh would ignore them.
-* Enhance "git repack" to not always use --all; this would be
- handy if the repository contains wagging heads like "pu" in
- git.git repository.
+ - diff-files would say unchanged.
-* Make rebase restartable; instead of skipping what cannot be
- automatically forward ported, leave the conflicts in the work
- tree, have the user resolve it, and then restart from where it
- left off [mechanism DONE; in pu].
+ - diff-index without --cached acts the same way as diff-index
+ --cached.
-* 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].
+* 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.
-* Updated git-changes-script Jeff Garzik needs [Inquiry for
- external spec sent out with a quick hack. Will know if that
- is what he needs hopefully soon].
+ <43CC695E.2020506@codeweavers.com>
-* Make sure we do reasonable thing on binary files even in
- cherry-pick and rebase. [mechanism DONE; rebase in pu]
+* 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.
-* Customizable init-db. Personally I think template mechanism
- is good enough. Otherwise, maybe add hooks/post-init-db.
+ <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
+* Perhaps a smarter HTTP anonymous download via CGI.
-Technical (trivial)
--------------------
+* Prepare to enable "always use symbolic refs for HEAD" patch.
+ We need a timeline to force Porcelains to get ready. All the
+ major ones should be ready now.
+
+* 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.
+
+* daemon --strict-symlink.
-* Stop installing the old-name symlinks [DONE].
+* daemon --no-user-dir, to make ~user still work with
+ --base-path. They ought to be independent.
-* 'git merge-projects'?
+* daemon --base-path does not apply automatically to whitelist
+ somehow feels wrong. If somebody cares enough, accept
+ patches.
- Subject: Re: Merges without bases
- References: <1125004228.4110.20.camel@localhost.localdomain>
- Date: Thu, 25 Aug 2005 15:26:36 -0700
- Message-ID: <7vvf1tps9v.fsf@assigned-by-dhcp.cox.net>
+* Perhaps detect cloning request in upload-pack and cache the
+ result for next cloning request until any of our refs change.
-* 'git lost-and-found'? Link dangling commits found by
- fsck-objects under $GIT_DIR/refs/lost-found/. Then
- show-branch or gitk can be used to find any lost commit.
- [DONE]
+* Perhaps accept patch to optionally allow '--fuzz' in
+ 'git-apply'. am/applymbox is _not_ the place to do it.
- Do not name it /lost+found/; that would probably confuse
- things that mistake it a mount point (not our code but
- somebody else's).
+* Allow 'git apply' to accept GNU diff 2.7 output that forgets
+ to say '\No newline' if both input ends with incomplete
+ lines.
+
+* Perhaps deal with "Files differ" (binary diff) in non C
+ locales.
+
+* Maybe grok PGP signed text/plain in applymbox as well.
+
+* 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)
+-------------------
-* Add simple globbing rules to git-show-branch so that I can
- say 'git show-branch --heads "ko-*"' (ko-master, ko-pu, and
- ko-rc are in refs/tags/).
+* Use parent info in 'diff-tree --stdin'.
-* 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:
+* git-proxy should be spawned with sh -c 'command' $1 $2.
- git-update-index
- git-ls-files
- git-diff-files
- git-diff-index
- git-diff-tree
- git-rev-list
- git-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`).
projects / git.git / blobdiff