{"thread":{"id":"1707","subject":"What's in git.git today.","startedAt":"2005-09-01T01:20:23Z","lastAt":"2005-09-01T01:20:23Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"7982","messageId":"7vhdd560tk.fsf@assigned-by-dhcp.cox.net","threadId":"1707","inReplyTo":null,"subject":"What's in git.git today.","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-09-01T01:20:23Z","receivedAt":"2005-09-01T01:20:23Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I've been doing some clean-ups, mostly in the documentation\narea.  The tutorial reachable from the main gitweb page should\nlook a lot nicer and use glossary words more consistently then\nbefore.  I think its 'Packing your repository' section should be\nreplaced with more general 'Feeding and caring for your\nrepository' section, that talks not just about packing, but the\ngeneral repository organization issues like:\n\n - Public (naked) repository vs working tree repository.\n - What each hook is for.\n - Why pack?  When to pack?\n - Why prune?  When to prune?\n - Should I use objects/info/alternates?\n - Transport specific hints:\n   - For dumb transports, update-server-info is a must.\n   - For git: transport, 'git-daemon-export-ok' is needed.\n   - Git-native transport is inefficient when bootstrapping.\n\nBut other than that I consider the tutorial in a pretty good\nshape.\n\n... and that can only mean one thing.  I want to really start\n1.0pre, but I'd settle for 0.99.6 for now.\n\nBy the way.  A couple of people privately asked me what the\nextra \"branch\" `todo` is doing in the git.git repository.\n\nThat \"branch\" does not share any tree namespace with the real\ngit source.  Its tree has only one blob, TODO, and keeps my\nnotes on the current progress.  So you should *not* do this:\n\n    $ git clone kernel.org/pub/scm/git/git.git/\n    $ git pull . todo\n\nYou would end up merging completely different things together if\nyou did so.\n\nThere is another mystery branch called \"dbrt-test\"; I'll blow it\naway after we are done with the read-tree change Daniel is\nworking on.  The changed read-tree code looks much cleaner and I\nlike the general direction it is going, but there are some\ndebugging ahead of us.  That mystery branch holds standalone\ntest suite that is supposed to be extracted in a repository\nindependent from the main git repository, so please do not merge\nfrom it, either.\n"}]}