Sorry, and one more: $ git ls-remote . f11c723119cd9938e91e1ed5328ef143fb477f15 HEAD 138ea08f9680a8def085b793c9cee70eed0e1f3b refs/heads/master 75290a081feebcc4265825d017d9af07c7646951 refs/heads/remotebranch f11c723119cd9938e91e1ed5328ef143fb477f15 refs/heads/mybranch 138ea08f9680a8def085b793c9cee70eed0e1f3b refs/remotes/origin/HEAD 138ea08f9680a8def085b793c9cee70eed0e1f3b refs/remotes/origin/master 75290a081feebcc4265825d017d9af07c7646951 refs/remotes/origin/remotebranch f11c723119cd9938e91e1ed5328ef143fb477f15 refs/remotes/origin/mybranch Thank you!! -Irene Michael J Gruber wrote: > > ir0s venit, vidit, dixit 21.08.2008 17:35: >> Sorry if you get this twice, oddly my first attempt to send this bounced. >> Thank you for all the good advice however, none of it seemed to resolve >> my >> issue. >> >> Attempting to call: >> $git push origin mybranch >> >> Results in the same message: Everything up to date =/ >> I also tried to call $git fetch origin just in case, and doing a pull >> doesn't return anything (which makes sense, no one pushed anything to the >> branch -- although I seem to be the only one with this issue.) >> >> Could my branch have somehow diverged from the origin remotebranch? >> >> -- Irene > > What do the following report: > > git ls-remote origin > git ls-remote . > git log --pretty=oneline mybranch...origin/remotebranch > > Michael > > -- > 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 > > -- View this message in context: http://n2.nabble.com/Local-branch-ahead-of-tracked-remote-branch-but-git-push-claims-everything-up-to-date-tp736663p740670.html Sent from the git mailing list archive at Nabble.com. -- 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
