Um, sheesh, ok. :) I can do that too. (Homer Simpson Doh! moment.) I ran 'svn info' on my local svn tree. I show revision 1261450. The web site shows 1262727. Should I update my local tree svn before the big git day? That is, will I be able to convert my local svn tree to git to minimize download time? Darrell

Okay, I'm reading the wiki about git. In the checkout section the text implies the new local tree will be a directory named 'tde', same as upstream. Currently my Trinity svn tree is in my build directory under the name src_trinity_svn. I would like to use a similar name, such as src_trinity_git. If I understand correctly, I do this: cd $BUILDDIR git clone http://scm.trinitydesktop.org/scm/git/tde src_trinity_git cd src_trinity_git ./scripts/switch_all_submodules_to_head_and_clean * Is that correct? * I'm on a nominal broadband connection. About how many GB will I download with the new git tree? Although I submit patches, I'm not a seasoned developer and I have no desire to muck with the upstream git tree. I want only to maintain a local tree to build and test packages. If I understand correctly I do this: (If I do not change my local tree) cd $BUILDDIR/src_trinity_git git pull (If I change my local tree) cd $BUILDDIR/src_trinity_git ./scripts/commit_all_submodules * Is that correct? Lastly, no pressure intended, only curiosity that kills the cat, any estimate when git will go public? Or, can I create a local tree now and update daily but just don't use the tree until git goes public? Thanks Darrell