From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Russell, Scott" <Scott.Russell2@ncr.com>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>,
'Emily Shaffer' <emilyshaffer@google.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: pull failed - why should I receive this message.
Date: Fri, 24 Sep 2021 20:45:35 +0000 [thread overview]
Message-ID: <YU4475ZbWfnvKomP@camp.crustytoothpaste.net> (raw)
In-Reply-To: <BN6PR15MB1426EBF10C9E8634EF317DDBCBA49@BN6PR15MB1426.namprd15.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On 2021-09-24 at 20:13:15, Russell, Scott wrote:
> Brian,
>
> You are correct. This is a build system. And your responses are the most useful so far.
>
> "git fetch origin" - okay
>
> For this one, is there a way to specify just the head? I just want the latest - and don't want to try to figure out what 'Revision' may be.
>
> "git checkout -f REVISION"
Pretend the branch you want to operate on is called "main". Assuming
that your remote is origin, then you can write "git checkout -f
origin/main", or, if you want to be more precise, "git checkout -f
refs/remotes/origin/main". That will check out whatever's at the tip of
main.
Note that doing that will result in a detached HEAD, which probably
doesn't matter for you. In case it does, you can check out your local
branch to match it by doing "git checkout -f -B main refs/remotes/origin/main".
That will make sure you're on a branch called "main" and will reset it
to whatever was on the tip of main when you did your fetch. If you
wanted your local branch to be called "dev" instead, you could do this:
git checkout -f -B dev refs/remotes/origin/main
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2021-09-24 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 14:48 pull failed - why should I receive this message Russell, Scott
2021-09-24 17:28 ` Emily Shaffer
2021-09-24 17:34 ` Russell, Scott
2021-09-24 18:00 ` Randall S. Becker
2021-09-24 18:36 ` Russell, Scott
2021-09-24 18:39 ` Emily Shaffer
2021-09-24 18:52 ` Russell, Scott
2021-09-24 20:03 ` brian m. carlson
2021-09-24 20:13 ` Russell, Scott
2021-09-24 20:45 ` brian m. carlson [this message]
2021-09-24 20:49 ` Russell, Scott
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=YU4475ZbWfnvKomP@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=Scott.Russell2@ncr.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.com \
/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