Git development
 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: Tue, 06 Oct 2026 13:48:07 -0700	[thread overview]
Message-ID: <xmqqbj96d08o.fsf@gitster.g> (raw)
In-Reply-To: <20261006184542.V9Kze%taahol@utu.fi> (Tuomas Ahola's message of "Tue, 6 Oct 2026 21:45:42 +0300")

Tuomas Ahola <taahol@utu.fi> writes:

> With an evil merge, or by stacking my topic on top of Julia's---which I think
> is the cleaner solution because that way I can add gt-2 as a linter exemption
> in the patch itself and explain it in the commit message.

OK, then I'll use a synthetic base (i.e., not directly on 'master'
or 'maint', but topic(s) by others merged to a more natural base)
when queuing your rerolled patch.

Thanks.

  reply	other threads:[~2026-10-06 20:48 UTC|newest]

Thread overview: 28+ 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 [this message]
2026-10-06 17:34     ` Julia Evans

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=xmqqbj96d08o.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox