[email protected] wrote: > I have several development or personal branches in my tree, and they > should not be published. So I don't think it a good idea to send you > whole .git/ in my local tree. > >
I *think* what you would do in this case (just for reference), is to create a new empty repo, then you would fetch locally just the branches you cared about from the original repo, then remove the remote repo. It's possible you then need to cleanup the remote data in your .git directory (not sure), but I believe this can also be achieved most simply by just recloning this new repo to a fresh directory, however I believe the remotes are just a subdirectory in your .git? Alternatively you could create a new bare repo, then *push* just the branches you want to export to the new repo. Run a repack and a gc on the new repo Finally, assuming you have local access, have you tried a "git gc" on the broken data? I have never seen a broken git repo before, so I'm actually a little curious to hear how this works out? (In contrast, svn seems to have loads of scary errors near every time I try and do a change and it doesn't go flawlessly...) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
