From: Erik V. <eri...@xs...> - 2012-10-06 15:33:05
|
Brett, > "git fetch" is all you need. It will fetch all changesets across all remote > branches. I think you have overlooked this remark of mine: >> Please note, that I have configured the bare > > 'git push'/'git pull' to transmit branch 'master' only.+ ...which also applies to git fetch. > Once you do a fetch or pull without arguments, it should pull down > references to any branches you're missing. No, and that is not what I had always intended either, see above. I don't want branches that I'm not interested in. I want to keep it simple. I guess that's unusual... > If this fails, can you show what "git config --list" and "git branch -r" shows? git config -l: core.symlinks=false core.autocrlf=true color.diff=auto color.status=auto color.branch=auto color.interactive=true pack.packsizelimit=2g help.format=html http.sslcainfo=/bin/curl-ca-bundle.crt sendemail.smtpserver=/bin/msmtp.exe diff.astextplain.textconv=astextplain rebase.autosquash=true user.name=Erik Vos user.email=eri...@xs... branch.autosetuprebase=always core.repositoryformatversion=0 core.filemode=false core.logallrefupdates=true core.autocrlf=false remote.origin.url=ssh://ev...@ra.../gitroot/rails/rails remote.origin.fetch=refs/heads/master:refs/remotes/origin/master remote.origin.push=refs/heads/master:refs/heads/master branch.master.remote=origin branch.master.merge=refs/heads/master branch.autosetuprebase=always git branch -r: origin/master Thinking again, I might remove remote.origin.fetch, leaving remote.origin.push in place. Or can I add just a second branch? Erik. |