git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: [PATCH 2/2] doc: add new Git tutorial for beginners

From
RKRichard Kerry <richard.kerry@atos.ai>
Date
Oct 26, 2026, 16:03 UTC
Message-ID
<AS4PR02MB8336459DD1A4537A43A5C724EB612@AS4PR02MB8336.eurprd02.prod.outlook.com>
In-Reply-To
<60D4F9B6-0858-43FC-8C2A-B6200640961E@jvns.ca>
Hi Julia, Team,
There was a request earlier for notes from Windows Git users, so as I am one I thought I might respond a little.
I use Git mostly via a GUI app.  I do understand that documentation for Git proper needs to treat it as command-line as all the GUIs are a bit different.  I think they all work via the CLI version and all that I use do always show the commands, so I quite understand that documentation needs to be done like that.
However....

Windows users don't use vim (or vi). Windows users don't use ssh.

I'm sure neither of those are completely true, so please no-one write in and say that I'm wrong, but I think a lot of Windows Git users won't do so, and will feel such mentions are not aimed at them and may take it that the whole document isn't either.
I'm sure I've read somewhere that ssh is a nightmare to set up on Windows, so a first-class mention of it may put off Windows users.  It might perhaps get a note that it's for Linux/Unix/etc users only (or only-ish).  Anyway, I've been developing on Windows for about 30 years and using Git for about eight, and never needed ssh for anything.  Https is all that I've used for GitHub and BitBucket, which you might consider likely to be the most common servers users might see.  And bearing in mind that GitHub has on-prem versions that may be found in corporate settings.  I'm not sure how easy it is to set up a local Git server by other means as I've never really tried.
Vim I think is very uncommon on Windows.  The only editor that is universal is NotePad, but I don't think that would be used much for serious development.  I use versions of Visual Studio but Visual Studio Code (no relation) may be more common nowadays.  For general editing I may use emacs for historical reasons, but I suspect that's nearly as rare on Windows as vim.  Something like NotePad++ would be better.  But then again, it isn't universal.
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.
Kind regards,

Richard Kerry BNCS Engineer - Media Competency Centre MidCity Place, 71 High Holborn - London WC1V 6EA - UK atos.ai

Show 27 quoted lines
> -----Original Message-----
> From: Julia Evans <julia@jvns.ca>
> Sent: 20 October 2026 19:23
> To: Junio C Hamano <gitster@pobox.com>
> Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>; git@vger.kernel.org
> Subject: Re: [PATCH 2/2] doc: add new Git tutorial for beginners
>
> Caution: External email. Do not open attachments or click links, unless this email
> comes from a known sender and you know the content is safe.
>
>
> >
> >> +Step 10: Create an SSH key (if needed)
> >> +-------------------------------------
> >
> > Even though AsciiDoc implementations are somewhat lenient to allow
> > difference by a char or two, but the number of hyphens there must
> > match the number of chars on the previous line, so add one '-'.
>
> I meant to reply to this one. I wonder if it would be better to update all the
> headings to use a different form, like this, because it's easy to accidentally get the
> number of `-` characters wrong when editing a heading.
>
> == Step 10: Create an SSH key (if needed)
>
> I don't feel strongly about that though, happy to stay consistent with how other
> pages do it.
Atos is a trading name used by the Atos group. The trading entity is registered in England and Wales: Atos IT Services UK Limited (registered number 01245534). The registered office is located at: Second Floor, MidCity Place, 71 High Holborn, London, WC1V 6EA. The VAT No. is: GB232327983. This e-mail and the documents attached are confidential and intended solely for the addressee and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use, or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended, or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.
Previous: Junio C HamanoNext: Julia Evans
Message 19 of 53 in “WIP: doc: add new git tutorial”
  1. 0/2 WIP: doc: add new git tutorialJulia Evans via GitGitGadget, Oct 6, 2026
  2. 1/2 doc: remove gittutorialJulia Evans via GitGitGadget, Oct 6, 2026
  3. 2/2 doc: add new Git tutorial for beginnersJulia Evans via GitGitGadget, Oct 6, 2026
  4. D. Ben KnobleOct 7, 2026
  5. Julia EvansOct 19, 2026
  6. Ben KnobleOct 19, 2026
  7. Julia EvansOct 19, 2026
  8. D. Ben KnobleOct 19, 2026
  9. Junio C HamanoOct 20, 2026
  10. Julia EvansOct 20, 2026
  11. Junio C HamanoOct 20, 2026
  12. Junio C HamanoOct 20, 2026
  13. Junio C HamanoOct 20, 2026
  14. Junio C HamanoOct 20, 2026
  15. Junio C HamanoOct 21, 2026
  16. Julia EvansOct 21, 2026
  17. Julia EvansOct 20, 2026
  18. Junio C HamanoOct 20, 2026
  19. Richard KerryOct 26, 2026
  20. Julia EvansOct 26, 2026
  21. Julia EvansOct 26, 2026
  22. Junio C HamanoOct 26, 2026
  23. Julia EvansOct 26, 2026
  24. Junio C HamanoOct 26, 2026
  25. D. Ben KnobleOct 7, 2026
  26. 0/2 doc: add new git tutorialJulia Evans via GitGitGadget, Oct 19, 2026
  27. 1/2 doc: remove gittutorialJulia Evans via GitGitGadget, Oct 19, 2026
  28. 2/2 doc: add new Git tutorial for beginnersJulia Evans via GitGitGadget, Oct 19, 2026
  29. Junio C HamanoOct 20, 2026
  30. Ben KnobleOct 20, 2026
  31. Julia EvansOct 20, 2026
  32. Tuomas AholaOct 20, 2026
  33. Junio C HamanoOct 20, 2026
  34. 0/2 doc: add new git tutorialJulia Evans via GitGitGadget, Oct 23, 2026
  35. 1/2 doc: remove gittutorialJulia Evans via GitGitGadget, Oct 23, 2026
  36. 2/2 doc: add new Git tutorial for beginnersJulia Evans via GitGitGadget, Oct 23, 2026
  37. Ben KnobleOct 23, 2026
  38. Julia EvansOct 27, 2026
  39. Ben KnobleOct 27, 2026
  40. Julia EvansOct 27, 2026
  41. 0/2 doc: add new git tutorialJulia Evans via GitGitGadget, Oct 28, 2026
  42. 1/2 doc: remove gittutorialJulia Evans via GitGitGadget, Oct 28, 2026
  43. Junio C HamanoOct 28, 2026
  44. Julia EvansOct 30, 2026
  45. Junio C HamanoOct 30, 2026
  46. 2/2 doc: add new Git tutorial for beginnersJulia Evans via GitGitGadget, Oct 28, 2026
  47. Junio C HamanoOct 28, 2026
  48. Julia EvansOct 30, 2026
  49. Junio C HamanoOct 30, 2026
  50. Junio C HamanoOct 30, 2026
  51. 0/2 doc: add new git tutorialJulia Evans via GitGitGadget, Oct 30, 2026
  52. 1/2 doc: remove gittutorialJulia Evans via GitGitGadget, Oct 30, 2026
  53. 2/2 doc: add new Git tutorial for beginnersJulia Evans via GitGitGadget, Oct 30, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.