From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 1/2] gittutorial: drop early mention of origin
Date: Sat, 15 Apr 2023 19:29:10 +0200 [thread overview]
Message-ID: <36a8ede4c83ff6d88c9d49bd64f1546262934c55.1681579244.git.martin.agren@gmail.com> (raw)
In-Reply-To: <cover.1681579244.git.martin.agren@gmail.com>
We don't have an origin at this point in the tutorial, so "Your branch
is up to date" won't actually show up in the output of `git status`.
This line was introduced in 8942821ec0 ("gittutorial: fix output of 'git
status'", 2014-11-13) in what looks like a mistake -- that commit mostly
just wanted to remove leading '#' characters.
Signed-off-by: Martin Ågren <martin.agren@gmail.com>
---
Documentation/gittutorial.txt | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
index 0e0b863105..33dd5a2cba 100644
--- a/Documentation/gittutorial.txt
+++ b/Documentation/gittutorial.txt
@@ -109,7 +109,6 @@ summary of the situation with 'git status':
$ git status
On branch master
Changes to be committed:
-Your branch is up to date with 'origin/master'.
(use "git restore --staged <file>..." to unstage)
modified: file1
--
2.40.0.406.g2798986c60
next prev parent reply other threads:[~2023-04-15 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 17:29 [PATCH 0/2] gittutorial: minor correction and monospacing Martin Ågren
2023-04-15 17:29 ` Martin Ågren [this message]
2023-04-20 21:15 ` [PATCH 1/2] gittutorial: drop early mention of origin Junio C Hamano
2023-04-15 17:29 ` [PATCH 2/2] gittutorial: wrap literal examples in backticks Martin Ågren
2023-04-20 21:33 ` Junio C Hamano
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=36a8ede4c83ff6d88c9d49bd64f1546262934c55.1681579244.git.martin.agren@gmail.com \
--to=martin.agren@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).