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].
+ update the SubmittingPatches.
* Talk about using rsync just once at the beginning when
initializing a remote repository so that local packs do not
* 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.]
+ [Deathmatch between Daniel's and Fredrik's ongoing.]
* HPA has two projects, klibc and klibc-kbuild, that have large
set of overlapping files in different paths (i.e. one has many
* 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].
+ for the best merge [DONE].
* We might want to optimize cloning with GIT native transport
not to explode the pack, and store it in objects/pack instead.
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.
+* Maybe a pack optimizer.
* Maybe an Emacs VC backend.
Technical (milder)
------------------
-* Tool renames [STARTED].
+* Define semantics for relative pathnames in objects/info/alternates.
+ Either relative to 'objects', or relative to the top of project tree
+ ;the latter is consistent with GIT_ALTERNATE_OBJECT_DIRECTORIES.
+ Perhaps would end up doing the former because we would want to be
+ consistent between a naked repository and a repository with working
+ tree [DONE].
-* Have Daniel's read-tree graduate from "pu" after plugging leaks.
+* Tool renames. Give fixup patch for at least Cogito and StGIT
+ [DONE].
-* Implement a merge backend using Daniel's read-tree.
+* Have Daniel's read-tree graduate from "pu" after plugging
+ leaks [DONE].
+
+* Implement a merge backend using Daniel's read-tree [DONE].
+
+* Rename 'git-merge-resolve' to 'git-merge-stupid' and
+ 'git-merge-multibase' to 'git-merge-resolve'; the former is
+ for historical curiosity and comparison purposes only and not
+ to be used in real applications so remove it from the default
+ strategies list [DONE].
* 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.
+ installation [DONE].
* Encourage concrete proposals to commit log message templates
we discussed some time ago.
-* Bug Martin for archimport script documentation.
+* Bug Martin for archimport script documentation [DONE].
-* More portability. I dropped a SunOS patch on the floor by
- somebody.
+* More portability [IN PROGRESS].
* Accept patches to cause "read-tree -u" delete a directory when
it makes it empty.
* Perhaps accept patches to do undo/redo.
+* Perhaps accept patch to optionally allow '--fuzz' in
+ 'git-apply'.
+
* Maybe grok PGP signed text/plain in applymbox as well.
* Perhaps a tool to revert a single file to pre-modification
* A tool to detect, show and prune already merged topic
branches.
+* "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.
+
+ Do not name it /lost+found/; that would probably confuse
+ things that mistake it a mount point (not our code but
+ somebody else's).
+
* Enhance "git repack" to not always use --all; this would be
handy if the repository contains wagging heads like "pu" in
git.git repository.
* Option to limit rename detection for more than N paths.
+* Marking copy seems to be broken when A,B => B,C rename
+ happens; we incorrectly say B stays, which makes the new B
+ copy of old A, not rename [DONE].
+
+* 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.
+
+* 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.
+* Deal with CDPATH [DONE].
+
+* Teach 'git format-patch' about 'git cherry' [DONE].
+
+* Make 'git bisect' easier to use by logging the earlier
+ good/bad choices and make it replayable [DONE].
+
+* Perhaps "git branch -d" to delete a branch. We probably need
+ some way to say "delete this branch because everything in this
+ should be merged in the master branch" and refuse the removal
+ if it is not true.
* 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
+ git-update-index
+ git-ls-files
+ git-diff-files
+ git-diff-index
+ git-diff-tree
+ git-rev-list
+ git-rev-parse
* In a freashly created empty repository, `git fetch foo:bar`
works OK, but `git checkout bar` afterwards does not (missing
projects / git.git / blobdiff