On Sep 21, 2009, at 4:40 PM, Tekkub wrote: > Yes, you'll need to clone again for each subdirectory with that > setup. There are ways to get git to share the space though, check > out git-clone's docs: > http://www.kernel.org/pub/software/scm/git-core/docs/git-clone.html > > Basically you would clone the main repo once from GitHub, then clone > from your local repo using the --shared flag. After you've cloned > locally, you can add a remote to github so that you can push from > that repo.
Ok, that's a good suggestion. But what if I only want one of the branches? For instance the deployed app doesn't need to have objects for the mockups and artwork. What I would really like is to be able to git clone a specific branch (which would create a new repo on my local disk and connect that branch to master). > I have a question here though... why do you want to do this? You're > basically going around and adding a bunch of complexity that, in the > end, lands you right back where you would be if you simply committed > everything as subdirectories in the same branch. It has a couple of advantages: 1. A more standard Rails setup (capistrano deployment would just work) 2. You only need to download the branches that you need (faster clone) 3. Branches can be added and removed to keep repo size down -- John Long http://wiseheartdesign.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
