Many open source projects (e.g. django ) have GIT mirrors, which in turn are forked for private or public development, GIT mirrors are kept up to date with git svn rebase. But the Pro GIT Book contains this explicit recommendation:
Ah, but the bliss of rebasing isnt without its flaws, which can be summed up on one line:
Do not overload the commits that you moved to the shared repository.
If you follow this guide, youll be smart. If you do not, people hate you, and friends and families will despise you.
When you overload things, youre abandoning existing commits and creating new ones that are similar, but different. If you push commits somewhere and others and basic work on them, and then you rewrite these commits with GIT rebase and push them again, employees will have to re-combine their work and everything will be messy when you try to get your work back into yours.
Are there open source mirrors like Django that violate the above rule above without overloading the public repo? If not, why not? If so, what cannot be done with these mirrors, which can be done with "regular" non-revised GIT projects? Sorry if this is an obvious question; I am new to git.