Hello Lachlan,
Thank you for your question about using git's sparse-checkout option to retrieve part of the kent repository. I'm not sure how you arrived at the "git pull" error messages - I followed the same process to create a local repository, and "git pull origin beta" worked just fine for me. The subsequent "git checkout -t -b beta origin/beta" gives me the same error that it gives you, but that's not a big surprise. The original "git pull" tried to bring part of the remote beta branch into your current local branch, which is probably titled master (you can try running "git branch" to confirm that). The -b flag to git checkout tells git that you want to create a new local branch and switch to it, but that's not compatible with updating paths. Thus, git gets confused.
You can try to set tracking information for your sparse repository with "git branch --set-upstream master origin/beta" (followed by git pull), but that may not be enough to fix whatever is broken with your repository. You might need to first run "git fetch" (or run the original "git remote add" with the -f option to perform a fetch) so that the branch information is available. If that does not help, we recommend that you either start from scratch and just check out the full repository, or else consult a different list for git technical support.
I hope this is helpful. If you have any further questions, please reply to gen...@soe.ucsc.edu or genome...@soe.ucsc.edu. Questions sent to those addresses will be archived in publicly-accessible forums for the benefit of other users. If your question contains sensitive data, you may send it instead to genom...@soe.ucsc.edu.
--
Jonathan Casper
UCSC Genome Bioinformatics Group
--