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
patch, perhaps ;-).
-Documentation
+Design issues
-------------
-* Help Jon Loeliger to find place in the documentation to place
- his drawing [DONE].
-
-* 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.
-
-* 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.
-* Do we still have missing docs? If so accept patches to finish
- them.
-
-* Accept patches to talk about "Whoops, it broke. What's
- next?" [Started].
-
-* Accept patches to make formatted tables in asciidoc to work
- well in both html and man pages (see git-diff(1)).
+* 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)
-------------------
-* 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]
-
-* 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].
-
* 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].
-
-* 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.
+ 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]
-* Maybe an Emacs VC backend.
-
-* 'git split-projects'? This requires updated 'git-rev-list' to
- skip irrelevant commits.
- Message-ID: <Pine.LNX.4.63.0509221617300.23242@iabervon.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]
-
-* Plug-in file-level merges [Post 1.0].
+* 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.
Technical (milder)
------------------
-* Binary package split. Plan laid out and discussion mostly
- done. [RPM side done; Debian side delegated]
+* 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>).
-* User-relative paths by Andreas Ericsson. [Need to ping]
+* 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>)
-* Proxing git:// connection by Paul Collins. [Need to ping]
+* 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 look at Cogito and see if I can help Pasky to adjust to
- the later core features?
+* 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>).
-* Perhaps detect cloning request in upload-pack and cache the
- result for next cloning request until any of our refs change.
+* Per user .gitconfig across repositories -- ongoing.
-* Encourage concrete proposals to commit log message templates
- we discussed some time ago.
+* Encourage competition between annotate vs blame. Maybe come
+ up with some nontrivial test cases.
-* Perhaps accept patches to do undo/redo.
+* Subprojects. Try "gitlink" -- sorry, stalled.
-* Perhaps accept patch to optionally allow '--fuzz' in
- 'git-apply'.
+* Rebase and checkout -m should be able to use recursive
+ strategy as well. These commands currently do not work across
+ renames.
-* Allow 'git apply' to accept GNU diff 2.7 output that forgets
- to say '\No newline' if both input ends with incomplete
- lines.
+* 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.
-* Maybe grok PGP signed text/plain in applymbox as well.
+ <43CC695E.2020506@codeweavers.com>
-* Enhance "git repack" to not always use --all; this would be
- handy if the repository contains wagging heads like "pu" in
- git.git repository.
+* 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.
-* 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].
+ <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
-* 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].
+* 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.
-* 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].
+* daemon --strict-symlink.
-* Make sure we do reasonable thing on binary files even in
- cherry-pick and rebase. [mechanism DONE; rebase in pu]
+* daemon --base-path does not apply automatically to whitelist
+ somehow feels wrong. If somebody cares enough, accept
+ patches.
-* Customizable init-db. Personally I think template mechanism
- is good enough. Otherwise, maybe add hooks/post-init-db.
+* Perhaps detect cloning request in upload-pack and cache the
+ result for next cloning request until any of our refs change.
+
+* Maybe grok PGP signed text/plain in applymbox as well.
Technical (trivial)
-------------------
-* Stop installing the old-name symlinks [DONE].
-
-* 'git merge-projects'?
-
- 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>
-
-* '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]
-
- Do not name it /lost+found/; that would probably confuse
- things that mistake it a mount point (not our code but
- somebody else's).
-
-* 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/).
+* 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.
- 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