I've been doing some clean-ups, mostly in the documentation
area. The tutorial reachable from the main gitweb page should
look a lot nicer and use glossary words more consistently then
before. I think its 'Packing your repository' section should be
replaced with more general 'Feeding and caring for your
repository' section, that talks not just about packing, but the
general repository organization issues like:
- Public (naked) repository vs working tree repository.
- What each hook is for.
- Why pack? When to pack?
- Why prune? When to prune?
- Should I use objects/info/alternates?
- Transport specific hints:
- For dumb transports, update-server-info is a must.
- For git: transport, 'git-daemon-export-ok' is needed.
- Git-native transport is inefficient when bootstrapping.
But other than that I consider the tutorial in a pretty good
... and that can only mean one thing. I want to really start
1.0pre, but I'd settle for 0.99.6 for now.
By the way. A couple of people privately asked me what the
extra "branch" `todo` is doing in the git.git repository.
That "branch" does not share any tree namespace with the real
git source. Its tree has only one blob, TODO, and keeps my
notes on the current progress. So you should *not* do this:
$ git clone kernel.org/pub/scm/git/git.git/
$ git pull . todo
You would end up merging completely different things together if
you did so.
There is another mystery branch called "dbrt-test"; I'll blow it
away after we are done with the read-tree change Daniel is
working on. The changed read-tree code looks much cleaner and I
like the general direction it is going, but there are some
debugging ahead of us. That mystery branch holds standalone
test suite that is supposed to be extracted in a repository
independent from the main git repository, so please do not merge
from it, either.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html