From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>,
Alex Henrie <alexhenrie24@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Philip Oakley <philipoakley@iee.email>,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: [PATCH v4 01/19] doc: pull: explain what is a fast-forward
Date: Mon, 7 Dec 2020 18:26:30 -0600 [thread overview]
Message-ID: <20201208002648.1370414-2-felipe.contreras@gmail.com> (raw)
In-Reply-To: <20201208002648.1370414-1-felipe.contreras@gmail.com>
We want users to know what is a fast-forward in order to understand the
default warning.
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
---
Documentation/git-pull.txt | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index 5c3fb67c01..e1605a81b3 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -38,6 +38,20 @@ as set by linkgit:git-branch[1] `--track`.
Assume the following history exists and the current branch is
"`master`":
+------------
+ A---B---C master on origin
+ /
+ D---E master
+------------
+
+Then `git pull` will merge in a fast-forward way up to the new master.
+
+------------
+ D---E---A---B---C master, origin/master
+------------
+
+However, a non-fast-forward case looks very different.
+
------------
A---B---C master on origin
/
--
2.29.2
next prev parent reply other threads:[~2020-12-08 0:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 0:26 [PATCH v4 00/19] pull: default ff-only mode Felipe Contreras
2020-12-08 0:26 ` Felipe Contreras [this message]
2020-12-08 0:26 ` [PATCH v4 02/19] pull: improve default warning Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 03/19] pull: refactor fast-forward check Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 04/19] pull: cleanup autostash check Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 05/19] pull: trivial cleanup Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 06/19] pull: move default warning Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 07/19] pull: display default warning only when non-ff Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 08/19] pull: trivial whitespace style fix Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 09/19] pull: introduce --merge option Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 10/19] pull: show warning with --ff Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 11/19] rebase: add REBASE_DEFAULT Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 12/19] pull: move configurations fetches Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 13/19] test: merge-pull-config: trivial cleanup Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 14/19] test: pull-options: revert unnecessary changes Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 15/19] pull: trivial memory fix Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 16/19] pull: add pull.mode Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 17/19] pull: add pull.mode=ff-only Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 18/19] pull: advice of future changes Felipe Contreras
2020-12-08 0:26 ` [PATCH v4 19/19] future: pull: enable ff-only mode by default Felipe Contreras
2020-12-08 0:57 ` [PATCH v4 00/19] pull: default ff-only mode Felipe Contreras
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=20201208002648.1370414-2-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=alexhenrie24@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=philipoakley@iee.email \
/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).