On Tue, 2012-01-24 at 14:41 -0500, Jeff King wrote: > On Tue, Jan 24, 2012 at 02:00:31PM -0500, Rick Bragg wrote: > > > I cloned a repo from /home/me/repo1 to /home/me/repo2. Then made > > changes and a new commit on repo1, then from repo1 did "git > > push /home/me/repo2 and it says Everything is up-to-date. How could > > this be? > > It's hard to say, since you didn't show us the exact commands you ran. > > One possible cause is that you made your commit on a detached HEAD, not > on a branch, and therefore pushing branches will have no effect. You can > check this by running "git status", which will report either your > current branch or "not currently on any branch". > > Another possible cause is that git is not trying to push the branches > that you think it is. > > For example, imagine repo1 has two branches, "master" and "foo", and the > "master" branch is checked out. When you clone it, the resulting repo2 > will have remote-tracking branches for both "master" and "foo", but will > only checkout the "master" branch. Now imagine you make commits on > "foo" in repo1, and then try to push. Git's default behavior is to push > only branches which match (by name) a branch on the destination. So we > would attempt to push "master" (which is up to date), but not "foo". > > You can see which branches are being considered in the push with "git > push -vv". If you want to push all branches, you can use "git push > --all", or read up on refspecs in "git help push". If you want to change > git-push's default behavior, read up on "push.default" in "git help > config". > > -Peff > Thanks, I went back a few commits and tried again and it works. I'm not sure what it was, I will have allot of reading to do. Thanks again! Rick -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html