From: Tuomas Ahola <taahol@utu.fi>
To: Julia Evans <julia@jvns.ca>
Cc: Ben Knoble <ben.knoble@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
<git@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] doc: add new git tutorial
Date: Tue, 20 Oct 2026 21:50:31 +0300 [thread overview]
Message-ID: <20261020185031.Atmmv%taahol@utu.fi> (raw)
In-Reply-To: <FAD8AD8D-1F2D-47DB-ACFA-C523865E2221@jvns.ca>
Julia Evans <julia@jvns.ca> wrote:
>
>
> > On Oct 19, 2026, at 10:24 PM, Ben Knoble <ben.knoble@gmail.com> wrote:
> >
> >
> >> Le 19 oct. 2026 à 21:24, Junio C Hamano <gitster@pobox.com> a écrit :
> >>
> >> "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
> >>
> >>> So far we've gotten 112 comments from 30ish beta testers who have tried to
> >>> learn Git for the first using this tutorial....
> >>
> >> And we waited for 10 hours after seeing this cover letter in
> >> anticipation, but the patches haven't appeared on the list archive.
> >> Does GGG need to be given a gentle nudge somehow?
> >
> > I received the v2 patches. I rather suspect the list did something interesting (or the archive), or that the messages were too big.
>
>
> I see the patches here in the list archive
> https://lore.kernel.org/git/6532e60e30864c9bccfe5be0731c6913aa44d188.1792421748.git.gitgitgadget@gmail.com/
Thanks. That works, and so does
nntp://nntp.lore.kernel.org/6532e60e30864c9bccfe5be0731c6913aa44d188.1792421748.git.gitgitgadget@gmail.com .
However, all these fail:
- nntp://public-inbox.org/6532e60e30864c9bccfe5be0731c6913aa44d188.1792421748.git.gitgitgadget@gmail.com
- nntp://gmane.io/6532e60e30864c9bccfe5be0731c6913aa44d188.1792421748.git.gitgitgadget@gmail.com
- https://marc.info/?i=6532e60e30864c9bccfe5be0731c6913aa44d188.1792421748.git.gitgitgadget@gmail.com
- https://lwn.net/ml/git/6532e60e30864c9bccfe5be0731c6913aa44d188.1792421748.git.gitgitgadget@gmail.com
Quite puzzling.
next prev parent reply other threads:[~2026-10-20 18:50 UTC|newest]
Thread overview: 25+ 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-20 18:22 ` Julia Evans
2026-10-20 18:30 ` 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 [this message]
2026-10-20 19:13 ` 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=20261020185031.Atmmv%taahol@utu.fi \
--to=taahol@utu.fi \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=julia@jvns.ca \
/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