All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans" <julia@jvns.ca>
Cc: "Richard Kerry" <richard.kerry@atos.ai>,
	 "git@vger.kernel.org" <git@vger.kernel.org>,
	 "Julia Evans" <gitgitgadget@gmail.com>,
	 "Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 2/2] doc: add new Git tutorial for beginners
Date: Mon, 26 Oct 2026 13:17:48 -0700	[thread overview]
Message-ID: <xmqq33tsqkr7.fsf@gitster.g> (raw)
In-Reply-To: <a8dc2d4e-bbe3-4190-b889-d9f1355e8d2d@app.fastmail.com> (Julia Evans's message of "Mon, 26 Oct 2026 15:14:53 -0400")

"Julia Evans" <julia@jvns.ca> writes:

>> In short, if it mentions of someone using ssh and vim, I immediately 
>> think they are a Linux user, and I may tend to skip those parts of an 
>> article, or even assume the whole thing is not aimed at me.
>
> This makes sense to me, and I agree it's important to be careful about
> how we talk about SSH and vim for the reasons you say.
>
> I think a lot about how to make sure that the Git documentation is
> trustworthy and credible, and when we suggest using tools that are
> unfamiliar or not commonly used, it reduces credibility and makes it
> more likely that people will leave to find information somewhere else.

OK, so shall I mark the topic on hold until you decide if I should
expect a reroll or we'll address the above in follow-up changes in
other topics in future?

Thanks.

  parent reply	other threads:[~2026-10-26 20:17 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 19:37 [PATCH 0/2] WIP: doc: add new git tutorial Julia Evans via GitGitGadget
2026-10-06 19:37 ` [PATCH 1/2] doc: remove gittutorial Julia Evans via GitGitGadget
2026-10-06 19:37 ` [PATCH 2/2] doc: add new Git tutorial for beginners Julia Evans via GitGitGadget
2026-10-07 19:48   ` D. Ben Knoble
2026-10-19 14:24     ` Julia Evans
2026-10-19 16:49       ` Ben Knoble
2026-10-19 20:42         ` Julia Evans
2026-10-19 21:14           ` D. Ben Knoble
2026-10-20 17:11   ` Junio C Hamano
2026-10-20 17:59     ` Julia Evans
2026-10-20 18:26       ` Junio C Hamano
2026-10-20 18:27       ` Junio C Hamano
2026-10-20 18:45         ` Junio C Hamano
2026-10-20 19:13           ` Junio C Hamano
2026-10-21 17:16             ` Junio C Hamano
2026-10-21 21:24               ` Julia Evans
2026-10-20 18:22     ` Julia Evans
2026-10-20 18:30       ` Junio C Hamano
2026-10-26 16:03       ` Richard Kerry
2026-10-26 19:14         ` Julia Evans
2026-10-26 20:03           ` Julia Evans
2026-10-26 20:17           ` Junio C Hamano [this message]
2026-10-26 20:22             ` Julia Evans
2026-10-26 20:54               ` Junio C Hamano
2026-10-07 19:26 ` [PATCH 0/2] WIP: doc: add new git tutorial D. Ben Knoble
2026-10-19 14:55 ` [PATCH v2 0/2] " Julia Evans via GitGitGadget
2026-10-19 14:55   ` [PATCH v2 1/2] doc: remove gittutorial Julia Evans via GitGitGadget
2026-10-19 14:55   ` [PATCH v2 2/2] doc: add new Git tutorial for beginners Julia Evans via GitGitGadget
2026-10-20  1:24   ` [PATCH v2 0/2] doc: add new git tutorial Junio C Hamano
2026-10-20  2:24     ` Ben Knoble
2026-10-20 12:18       ` Julia Evans
2026-10-20 18:50         ` Tuomas Ahola
2026-10-20 19:13     ` Junio C Hamano
2026-10-23 15:17 ` [PATCH v3 " Julia Evans via GitGitGadget
2026-10-23 15:17   ` [PATCH v3 1/2] doc: remove gittutorial Julia Evans via GitGitGadget
2026-10-23 15:17   ` [PATCH v3 2/2] doc: add new Git tutorial for beginners Julia Evans via GitGitGadget
2026-10-23 18:01   ` [PATCH v3 0/2] doc: add new git tutorial Ben Knoble
2026-10-27 14:30     ` Julia Evans
2026-10-27 15:19       ` Ben Knoble
2026-10-27 18:31         ` Julia Evans
2026-10-28 14:44 ` [PATCH v4 " Julia Evans via GitGitGadget
2026-10-28 14:44   ` [PATCH v4 1/2] doc: remove gittutorial Julia Evans via GitGitGadget
2026-10-28 18:01     ` Junio C Hamano
2026-10-28 14:44   ` [PATCH v4 2/2] doc: add new Git tutorial for beginners Julia Evans via GitGitGadget
2026-10-28 17:26     ` 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=xmqq33tsqkr7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=julia@jvns.ca \
    --cc=richard.kerry@atos.ai \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.