All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
	<git@vger.kernel.org>,
	 Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v2 0/2] [doc] Remove gittutorial-2
Date: Thu, 05 Nov 2026 11:28:09 -0800	[thread overview]
Message-ID: <xmqqld77t6wm.fsf@gitster.g> (raw)
In-Reply-To: <20261105180747.P-kMC%taahol@utu.fi> (Tuomas Ahola's message of "Thu, 5 Nov 2026 20:07:47 +0200")

Tuomas Ahola <taahol@utu.fi> writes:

>> > This topic has graduated to 'master', so we should be more than ready for the
>> > last bullet point.  Please pick up the rerolled ta/command-list-guides-sync-lint
>> > at <20261029184834.2273-1-taahol@utu.fi>.
>> >
>> > $ git cherry -v origin/seen ta/command-list-guides-sync-lint
>> > + 9a1ba61ac0e4491a4f028250be478cfcf05c9ef4 command-list.txt: add gitformat-loose(5) and gitpacking(7)
>> > + 5d36d7585956d17172012c8e42d77597524708e8 lint-docs: check the guide list in command-list.txt
>> 
>> Sorry, I have no idea what you are trying to say with that "git
>> cherry" output.
>> 
>
> Just double-checked that the topic is not in 'seen' (the lines are
> plus-marked).
>
>> Earlier you said "I can rebase mine on top".  Is the patch
>> <20261029184834.2273-1-taahol@utu.fi> the result of such rebasing?
>
> Yes it is.

Thanks.  From a cursory read, it seems that the thread has a review
comment by Julia which wasn't really answered yet.  Is it ready to
be picked up?

  reply	other threads:[~2026-11-05 19:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 20:25 [PATCH 0/3] [doc] Remove gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 1/3] " Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 2/3] [doc] Remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-09-28 20:25 ` [PATCH 3/3] [doc] Delete translations of gittutorial-2 description Julia Evans via GitGitGadget
2026-09-29  7:50 ` [PATCH 0/3] [doc] Remove gittutorial-2 Junio C Hamano
2026-09-29 10:42   ` Julia Evans
2026-09-29 11:09     ` Julia Evans
2026-09-30  7:50     ` Junio C Hamano
2026-10-01 22:21       ` Julia Evans
2026-10-02  7:38         ` Junio C Hamano
2026-09-29 21:58 ` Junio C Hamano
2026-09-29 22:24   ` Junio C Hamano
2026-09-30  6:15     ` Tuomas Ahola
2026-09-30 14:22       ` Junio C Hamano
2026-09-30 13:16     ` Julia Evans
2026-09-30 14:07       ` Kristoffer Haugsbakk
2026-09-30  6:00 ` Tuomas Ahola
2026-09-30 14:01   ` Julia Evans
2026-10-05 20:20 ` [PATCH v2 0/2] " Julia Evans via GitGitGadget
2026-10-05 20:20   ` [PATCH v2 1/2] doc: remove gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37     ` Kristoffer Haugsbakk
2026-10-05 20:20   ` [PATCH v2 2/2] doc: remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-10-05 20:37   ` [PATCH v2 0/2] [doc] Remove gittutorial-2 Junio C Hamano
2026-10-06  5:50   ` Tuomas Ahola
2026-10-06 17:17     ` Junio C Hamano
2026-10-06 18:45       ` Tuomas Ahola
2026-10-06 20:48         ` Junio C Hamano
2026-11-05  6:57       ` Tuomas Ahola
2026-11-05 17:52         ` Junio C Hamano
2026-11-05 18:07           ` Tuomas Ahola
2026-11-05 19:28             ` Junio C Hamano [this message]
2026-10-06 17:34     ` Julia Evans
2026-10-26 11:00       ` Tuomas Ahola
2026-10-26 12:10         ` Julia Evans
2026-10-26 13:13           ` Tuomas Ahola
2026-10-26 13:57             ` Julia Evans
2026-10-26 17:05             ` Junio C Hamano
2026-10-26 13:52 ` [PATCH v3 " Julia Evans via GitGitGadget
2026-10-26 13:52   ` [PATCH v3 1/2] doc: remove gittutorial-2 Julia Evans via GitGitGadget
2026-10-26 13:52   ` [PATCH v3 2/2] doc: remove references to gittutorial-2 Julia Evans via GitGitGadget
2026-10-26 22:36     ` Junio C Hamano
2026-10-26 17:15   ` [PATCH v3 0/2] [doc] Remove gittutorial-2 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=xmqqld77t6wm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=julia@jvns.ca \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=taahol@utu.fi \
    /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.