-
-
Save Saissaken/b555f2c0772bee56601f70df501b6c96 to your computer and use it in GitHub Desktop.
I had a failure at line 12 for master (rejection). But line 13 worked, which was the important part for me. Thank you!
Thank you 👍👍👍
Thanks! This worked great :).
I didn't need git rebase upstream/master and it still worked to get the latest tags/release
👍
Thanks for the tip. But my fork's remote is missing some refs. How do I push them to my fork remote?
For instance, there is refs/remotes/upstream/4.13
after I did git fetch upstream
, but after I pushed to my fork origin
remote, I do not have that ref in the origin
remote. I only have the old ones up to refs/remotes/origin/4.12
. How do I resolve this?
P.S. tags are indeed synchronized. I don't know the difference between tags and refs in remotes.
Thanks for the tip. But my fork's remote is missing some refs. How do I push them to my fork remote? For instance, there is
refs/remotes/upstream/4.13
after I didgit fetch upstream
, but after I pushed to my forkorigin
remote, I do not have that ref in theorigin
remote. I only have the old ones up torefs/remotes/origin/4.12
. How do I resolve this?P.S. tags are indeed synchronized. I don't know the difference between tags and refs in remotes.
It was somewhat a dumb question. The thing is a branch. I can use some suggestions on how to synchronize branches from upstream. I did something like the following but wasn't sure if it is correct.
git push origin refs/tags/4.13.1:refs/heads/4.13
only because 4.13.1 was the latest tag in 4.13. Maybe I should have pushed local 4.13 to remote refs/heads/4.13? But interestingly enough, for this particular repo, there are no local branches when I forked the upstream and cloned it to my local.
I did git branch
and got the following:
$ git branch
* master
Works. Thank you!
Thank you!
another "thank you." cleaned up what I thought was a hopeless loss.
Works perfectly .... thank you !!!
+1 Thanks!
+1