git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] gittutorial: drop early mention of origin
Date: Thu, 20 Apr 2023 14:15:43 -0700	[thread overview]
Message-ID: <xmqqr0sexnk0.fsf@gitster.g> (raw)
In-Reply-To: <36a8ede4c83ff6d88c9d49bd64f1546262934c55.1681579244.git.martin.agren@gmail.com> ("Martin Ågren"'s message of "Sat, 15 Apr 2023 19:29:10 +0200")

Martin Ågren <martin.agren@gmail.com> writes:

> 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`.

True.  The example is a repository created out of a tarball extract
and not a clone of anything.

Will queue.  Thanks.

> 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

  reply	other threads:[~2023-04-20 21:16 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 ` [PATCH 1/2] gittutorial: drop early mention of origin Martin Ågren
2023-04-20 21:15   ` Junio C Hamano [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqr0sexnk0.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=martin.agren@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).