git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Walton <noloader@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: What is so broken with pull
Date: Fri, 13 Mar 2020 11:26:32 -0400	[thread overview]
Message-ID: <CAH8yC8knZEmKyYc7TwmXRCd24nK9YgDo3EYfvH58QWP61ZHpwQ@mail.gmail.com> (raw)

'git pull' used to work for me. Then I tried to sync my branch with
upstream/master according to
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork.

Now this is the shit I am dealing with:

$ git pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=<remote>/<branch> android

$ git branch --set-upstream-to=https://github.com/noloader/openssl/android
android
error: the requested upstream branch
'https://github.com/noloader/openssl/android' does not exist
hint:
hint: If you are planning on basing your work on an upstream
hint: branch that already exists at the remote, you may need to
hint: run "git fetch" to retrieve it.
hint:
hint: If you are planning to push out a new local branch that
hint: will track its remote counterpart, you may want to use
hint: "git push -u" to set the upstream config as you push.


What is so broken with these workflows? Wht can't Git perform a simple
god damn sync? Where the hell did the information go? How did Got
manage to lose it?

             reply	other threads:[~2020-03-13 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 15:26 Jeffrey Walton [this message]
2020-03-13 15:49 ` What is so broken with pull Andrei Rybak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH8yC8knZEmKyYc7TwmXRCd24nK9YgDo3EYfvH58QWP61ZHpwQ@mail.gmail.com \
    --to=noloader@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).