+
Skip to content

docs: clarify FETCH_HEAD overwrite behavior in gittutorial #2008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −0
Open

docs: clarify FETCH_HEAD overwrite behavior in gittutorial #2008

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions Documentation/gittutorial.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -341,6 +341,11 @@ Alice already knows everything that leads to her current state (`HEAD`),
and reviews what Bob has in his state (`FETCH_HEAD`) that she has not
seen with this command.

[NOTE]
====
`FETCH_HEAD` is overwritten each time `git fetch` is run. If Alice fetches from another repository or branch afterward, `FETCH_HEAD` will refer to that most recent fetch result — not to Bob's branch anymore.
====

If Alice wants to visualize what Bob did since their histories forked
she can issue the following command:

Expand Down
Loading
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载