Tool Renames Plan
=================
- - In 0.99.8, we will still install the backward compatible
- symbolic links in $(bindir). These will however be removed
- before 1.0 happens.
+ - In 0.99.9, the backward compatible symbolic links in
+ $(bindir) will be removed.
- git-ssh-push and git-ssh-pull pair is not going away within
- this timeframe, if ever. Each of these old-name commands
- continues to invoke its old-name counterpart on the other
- end.
+ 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.
What to expect after 0.99.8
Documentation
-------------
+* Document the ref naming restrictions [DONE].
+
+* David Ho's report suggests whatchanged documentation should
+ mention -m as "commonly used options". Steal Linus'
+ response [DONE].
+
* Help Jon Loeliger to find place in the documentation to place
his drawing.
* Update tutorial to cover setting up repository hooks to do
common tasks.
-* Accept patches to finish missing docs.
+* Do we still have missing docs? If so accept patches to finish
+ them.
* Accept patches to talk about "Whoops, it broke. What's
next?".
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.
+ 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
Technical (milder)
------------------
+* Merlyn reports trouble with http fetch [Hopefully solved by
+ Nick's updates].
+
+* Maybe look at Cogito and see if I can help Pasky to adjust to
+ the later core features? Zack Brown's "cg-seek leaving empty
+ directories" problem is a good example of this.
+
+* Perhaps detect cloning request in upload-pack and cache the
+ result for next cloning request until any of our refs change.
+
+* Perhaps accept more "want"s in upload-pack and do something
+ intelligent about it [Ongoing, by Johannes].
+
+* Perhaps send less "want"s from fetch-pack [DONE by JS].
+
+* Look at svn importer Smurf has. There is a small cvsimport
+ update in his tree as well [DONE].
+
+* Decide the notation of "peeling the onion" operator, and
+ implement it in sha1_name.c. Perhaps postfix "^{}" to mean
+ "peel and expect anything", "^{blob}" to mean "peel and barf
+ unless blob". The current "^0" becomes shorthand for
+ "^{commit}". [DONE]
+
* Quote the URL so that libcurl's metecharacter mechanism would
not kick in [DONE].
Assuming writable $GIT_DIR is more acceptable, but the
working tree toplevel may not be in a rare usage pattern.
-* Perhaps accept more "want"s in upload-pack and do something
- intelligent about it.
-
-* Perhaps detect cloning request in upload-pack and cache the
- result for next cloning request until any of our refs change.
-
-* Perhaps send less "want"s from fetch-pack.
-
* Encourage concrete proposals to commit log message templates
we discussed some time ago.
lines.
* What to do with TABs and LFs in pathnames without breaking GNU
- patch? [Have patch in proposed updates. Discussion still
- ongoing with Paul.]
+ patch? [DONE -- go with GNU patch extension proposed by Paul].
+
+* Adjust apply.c to proposed GNU patch extension that quotes \n
+ and \t in C style, inside "". [DONE]
+
+* Adjust diff.c to the same. [DONE]
* Maybe grok PGP signed text/plain in applymbox as well.
state? People with BK background know this operation as
'clean'. 'git checkout [-f] ent [path...]' was suggested by
Matthias Urlichs which sounds a natural extention to what the
- command currently does.
+ command currently does [DONE with a prodding by Linus].
* Enhance "git repack" to not always use --all; this would be
handy if the repository contains wagging heads like "pu" in
git.git repository.
-* Internally split the project into non-doc and doc parts; add
- an extra root for the doc part and merge from it; move the
- internal doc source to a separate repository, like the +Meta
- repository; experiment if this results in a reasonable
- workflow, and document it in howto form if it does.
-
- The point is to make it possible to fork that part off to
- somebody else; then I do not have to maintain Documentation
- directory myself anymore, just like I simply slurp the latest
- gitk from Paul and not worry about it ;-).
-
* 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
Technical (trivial)
-------------------
+* Peter Hagervall's sparse fix [DONE].
+
+* Alex Riesen reported that hooks are in effect in tests.
+ Should fix [DONE].
+
* Disallow [\001-\040\177] byte values from ref names. Also we
need to disallow ':' (used in refspec), '^' and '~' (postfix
- "peel the onion" operators) and leading '+' (again used in
- refspec, as prefix "force update" operator) [DONE].
+ "peel the onion" operators), and '..' ("ref1..ref2" notation
+ becomes ambiguous otherwise) [DONE].
+
+* Update fetch-pack and clone-pack to ignore funny refs from the
+ other end, while making sure peek-remote does not discard them.
+ [DONE]
+
+* Update upload-pack to send tag^{}. This would hopefully help
+ Pasky's automated tag tracking, and also Martin's findtags.
+ [DONE]
+
+* Adjust update-index to quoted --index-info [DONE].
+
+* Prepare apply.c changes for maint branch (0.99.8e) [DONE].
+
+* Perhaps show ^{commit}, ^{tree} instead of ^{} from ls-remote? [NO]
+
+* Re-adjust maint branch for the above if we did so. [NOT NEEDED]
* short SHA1 naming is not enforcing uniqueness. Should fix [DONE].
* 'git repack' can be DOSed. Should fix [DONE].
-* Stop installing the old-name symlinks [POSTPONED, but before 1.0].
+* Stop installing the old-name symlinks [IN 0.99.9].
* 'git merge-projects'?
projects / git.git / blobdiff