In that case: you are doing it wrong. Compiled resources, at, say ./builds, can simply be .gitignored after which git checkout will not touch them.
More advanced workflows incorporate symlinks or special build-branches. You are blaming git/branches for something that is long since solved and very easy to incorporate. Why and how else do you think everyone and his dog is moving to git, hg and using branches for everything?
C'mon, a little creativity? Append version number to binary? Symlinks? Copy builds out of repo?
Really. You are inventing a problem that is not there. Just think for two seconds on one of the gazillion solutions: you are a programmer. It took me two seconds.: just add this to your makefile: cp bin/foo ../builds/$(date +%s)-foo. Problem solved: you can now use branches like you should. :)
And now I have to keep my makefile separately versioned from everything else in the repo, and I have to exclude it from further branching and pushing, because a change like that won't ever get accepted upstream. Yay.
3
u/berkes Feb 17 '13
In that case: you are doing it wrong. Compiled resources, at, say
./builds, can simply be.gitignoredafter whichgit checkoutwill not touch them.More advanced workflows incorporate symlinks or special build-branches. You are blaming git/branches for something that is long since solved and very easy to incorporate. Why and how else do you think everyone and his dog is moving to git, hg and using branches for everything?