patch, perhaps ;-).
-Documentation
--------------
+UI
+--
-* Take the updated tutorial by Bruce Fields very seriously. It
- is a quite good initiative.
+* Make "git branch -d foo" while on foo branch suggest "maybe
+ you want to go back to 'master'?"
Design issues
-------------
+* "intent to add" index entries?
+
* 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.
-* Doing a merge in a separate directory.
+* Doing a merge in a separate directory?
-* Subprojects. I think the "bind commit" approach has been
- outlined at sufficiently detailed level. Maybe find time to
- actually start prototyping it?
+* Make 'format-patch' take revision limiters similar to
+ rev-list. For example:
- <7vacdzkww3.fsf@assigned-by-dhcp.cox.net>
+ A C
+ ....---x---o---o---x---o---o
+ /
+ /
+ /
+ ....---x---o---o
+ B
+
+ we should be able to format commits 'o', without duplicates,
+ by:
+
+ $ git format-patch ^A ^B C
+
+ Currently the closest approximation is
+
+ $ git format-patch A..C B..C
+
+ which results in the last two commits including C formatted
+ twice.
Technical (heavier)
This needs a matching smart on the dumb protocol downloader.
-* 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]
-
Technical (milder)
------------------
+* Shallow clones.
+
+* Encourage competition between annotate vs blame. Maybe come
+ up with some nontrivial test cases.
+
+* Subprojects. I think the "bind commit" approach has been
+ outlined at sufficiently detailed level. Maybe find time to
+ actually start prototyping it?
+
+ <7vacdzkww3.fsf@assigned-by-dhcp.cox.net>
+
* 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.
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 does not feel quite right.
+ true merge commit anyway, but this does not feel quite right.
<20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
-* Perhaps a smarter HTTP anonymous download via CGI.
-
-* 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.
-
-* Prepare to enable "most of the things are installed in
- GIT_EXEC_PATH not in bindir". I do not plan to set bindir !=
- gitexecdir myself in the main Makefile I ship, but distos
- should be able to choose to do so.
-
-* Forbid/ignore pack names that do not conform to the convention
- sha1_pack_name() assumes and reject in check_packed_git_idx()
- [In "pu"]
-
-* 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.
-
* 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.
-* daemon --no-user-dir, to make ~user still work with
- --base-path. They ought to be independent.
-
* 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'. am/applymbox is _not_ the place to do it.
-
-* 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)
-------------------
-* s/naked/bare/g.
-
* git-proxy should be spawned with sh -c 'command' $1 $2.
* test scripts for the relative directory path stuff.
projects / git.git / blobdiff