On Sun, Jun 27, 2010 at 12:54 PM, Michael <[email protected]> wrote: > So, my problem appears to be running "git push michaeltyson master", > instead of just "git push michaeltyson". I don't really know what the > former even means, having long since forgotten why I was even running > it.
The second one is the one that's confusing, not the first one. The fact that the second one happens to be working for you just happens to be confusing you even more. "git push michaeltyson master" pushes your local branch called "master" to a branch called "master" on the remote repository named "michaeltyson". This is great if your local branch is actually called master. If it's not, you're going to have problems. Perhaps what you want is this: git push michaeltyson michaeltyson/master Which pushes the local branch called "michaeltyson/master" to a branch called "michaeltyson/master" on the remote repository named "michaeltyson". It's also the same thing as "git push michaeltyson" (usually, depending on your git configuration). However, it's also almost certainly not what you want: you want the branch to be called "master" on the remote repo, not "michaeltyson/master". > An aside - despite being on the 'michaeltyson/master' branch, which I > assume is the remote branch pointing at my fork on github, git branches do not "point at" other branches. And you can't be "on" a remote branch; you can only be on a local branch. So you're having severe misunderstanding problems here. Re-read Scott Chacon's email from earlier. The problem is you have a *local* branch called "michaeltyson/master". It is *not* a remote branch and has *nothing to do* with a remote branch. It should just be called "master". To fix it, do this: git branch -D master git branch -m michaeltyson/master master Now your original push command will work: git push michaeltyson master > 'git push' > with no arguments complained that 'You can't push to > git://github.com/potionfactory/potionstore.git';. That's the Push URL > for the 'master' branch, which I wasn't even on! No, it's definitely not the Push URL. Push URLs on github don't start with git://. You can't push to any URL starting with git://. > Why doesn't git know > to use the push URL for the current branch? Branches don't have push URLs. Repositories have push URLs. > Correct me if I'm wrong, but I don't think there's any problems with > the branches - michaeltyson/master is a remote, which seems to be > correctly formatted and named, according to the docs I've read and > their corresponding examples, anyway. I chose not to revert to the > master branch as you suggested, as that took me straight back to the > original project, which I'd since forked. If you're going to ask people for advice, you'd be better off actually following their advice rather than ignoring it :) Scott was right. Fix it and your problems should go away. Have fun, Avery -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/github?hl=en.
