* Update the SubmittingPatches document to add MUA specific
hints on how to disable unwanted MIME and flowed-text by
- collecting past list postings [DONE]. Accept patches from
- people who was hit by shiny blue bat to update the same.
+ collecting past list postings [DONE].
+
+* Accept patches from people who were hit by shiny blue bat to
+ update the SubmittingPatches [ONGOING].
* 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.
-* Update tutorial to cover shared repository style a bit more,
- maybe with a toy project that involves two or three
- repositories.
+* Review the existing docs and see if the repository
+ organization needs to be clarified further [STILL NEEDSWORK].
+
+* Update tutorial to cover shared repository style a bit more
+ [DONE].
+
+* Maybe update tutorial with a toy project that involves two or
+ three developers..
+
+* Document the hooks.
* Update tutorial to cover setting up repository hooks to do
- common tasks. [IN PROGRESS]
+ common tasks.
+
+* Get help to properly use asciidoc in tutorial [Heck, ended up
+ learning it myself, DONE].
-* Get help to properly use asciidoc in tutorial.
+* Maybe justify and demonstrate an Octopus in the tutorial
+ [STILL NEEDSWORK].
-* Maybe justify and demonstrate an Octopus in the tutorial. Add
- it to the glossary.
+* Add Octopus to the glossary [Thanks Johannes, DONE].
Technical (heavier)
* 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.
- [Underway. Thanks Daniel and Fredrik for taking an
- initiative.]
+ [STARTED TESTING PATCH FROM DANIEL]
* 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 an Emacs VC backend.
+
Technical (milder)
------------------
checkout" without -f gets confused. Figure out a good way to
handle this. [DONE]
- We still have the same issue with "git fetch". Fetching into
+* We still have the same issue with "git fetch". Fetching into
the branch one is on _may_ need to do the same thing as
fetching into anonymous head and then do the resolve. At
least it needs a warning. [DONE]
* "git commit -m" should work for initial commits and perhaps
merge commits as well. Warning about merge is still a good
thing to do, while -m is useful in scripted non-interactive
- use, so we need to be careful. [DONE - waiting for response]
+ use, so we need to be careful. [DONE]
* Encourage concrete proposals to commit log message templates
we discussed some time ago.
+* Test apply.c patches from Robert Fitzsmons and have them
+ graduate to "master" branch.
+
* Bug Ryan and work with him to update send-email easier to use.
[Resurrected it for Debian build.]
http://www.cs.berkeley.edu/~ejr/gits/git.git#portable
- [Looked at it. Maybe promising. Maybe not.]
+ [Applied. Burned by one of them and backed out, but otherwise
+ looks OK.]
* Accept patches to cause "read-tree -u" delete a directory when
it makes it empty.
* MIMEified applymbox to grok B and Q encodings in headers and
turn them into UTF-8; unwrap QP; explode multipart.
+ [DONE. waiting for a bug to happen ;-) ]
+
+* Maybe grok PGP signed text/plain in applymbox as well.
+
+* Perhaps a tool to revert a single file to pre-modification
+ state? git-cat-file blob `git-ls-files | grep foo` >foo or
+ git-cat-file blob `git-ls-tree HEAD foo` >foo? What should
+ the command be called? git-revert is taken so is
+ git-checkout.
* "git cherry-pick" that applies the patch an existing commit
introduces in its ancestry chain, possibly using the 3-way
- merge machinery. [Done. Needs documentation.]
+ merge machinery. [DONE]
-* Update rebase using the cherry-pick command. [Done]
+* Update rebase using the cherry-pick command. [DONE]
-* Redo "git revert" using 3-way merge machinery. [Done]
+* Redo "git revert" using 3-way merge machinery. [DONE]
* A tool to detect, show and prune already merged topic
branches.
* Set up an automated documentation rebuilding procedure at
- kernel.org, using update hook mechanism. [Almost, but not
- quite.] Describe it in a howto form [Done].
+ kernel.org, using update hook mechanism. [DONE]
+
+* Describe automated documentation rebuilding in a howto form
+ [DONE].
* Enhance "git repack" to not always use --all; this would be
handy if the repository contains wagging heads like "pu" in
git.git repository.
+* Accept and apply "git repack --all" patch, except the part
+ that removes the existing packs. [DONE]
+
* 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.
-* Add names to all nodes in show-branch.
+* Add names to all nodes in show-branch [DONE].
* Option to limit rename detection for more than N paths.
diff-tree
rev-list
+
+Initial repository Gotchas
+--------------------------
+
+* `git fetch foo:bar` works OK, but `git checkout bar`
+ afterwards does not (missing `.git/HEAD`)
+
+* `git commit -s` did not add signoff for initial commit [DONE].
+
+* `git status` does not work well when missing `.git/HEAD` [DONE].
+
+* `git log` either; git-log-script uses die which does not exist
+ [DONE].
+
\f
Local Variables:
mode: text
projects / git.git / blobdiff