Part of the point of git is that you can commit and share patches without pushing them to the main branch and so can make sure things are clean before you do.
Specifically - make sure there are no commits adding README.md files to the root directory - make sure there are no "Merge " commits in the history.
You can use git log to look for such commits and git rebase -i HEAD~some_number To edit the last some_number of branches (to delete them clean up the commit messages, merge branches).
Some updated instructions have been added to the wiki page. And, please rerun setup_git next time you pull. That will make things a bit cleaner, I think.
On Apr 22, 2013, at 3:17 PM, Daniel Russel drussel@gmail.com wrote:
> Part of the point of git is that you can commit and share patches without pushing them to the main branch and so can make sure things are clean before you do. > > Specifically > - make sure there are no commits adding README.md files to the root directory > - make sure there are no "Merge " commits in the history. > > You can use git log to look for such commits and > git rebase -i HEAD~some_number > To edit the last some_number of branches (to delete them clean up the commit messages, merge branches). >
-
Daniel Russel