git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 Josh Soref <gitgitgadget@gmail.com>,
	 git@vger.kernel.org
Subject: Re: [PATCH 1/3] t6429: update comment to mention correct tool
Date: Mon, 17 Nov 2025 14:10:43 -0800	[thread overview]
Message-ID: <xmqq346cia3g.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BGhU7KfRo9pS-PzRQea3YpU4qxG9iuJzxmWK=mvdhZrsw@mail.gmail.com> (Elijah Newren's message of "Mon, 17 Nov 2025 11:54:13 -0800")

Elijah Newren <newren@gmail.com> writes:

>> And nothing seems to have happened since then.  I can amend the typo
>> away if you want after the release before starting to merge topics
>> down to 'next' again.
>
> If it's easier for you to amend locally, that's great, but if it's
> easier for you to have me send a re-rolled series, I've got it all
> queued up and ready to go -- it's just this one typofix.  Sorry for
> not getting it sent out a little sooner.

I grew very fond of "git commit --fixup amend:<that-commit>"
followed by "git rebase --keep-base --autosquash", so it is not a
problem for me.

Thanks.


  reply	other threads:[~2025-11-17 22:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 18:01 [PATCH 0/3] Fix another crazy rename assertion Elijah Newren via GitGitGadget
2025-11-03 18:01 ` [PATCH 1/3] t6429: update comment to mention correct tool Elijah Newren via GitGitGadget
2025-11-07 14:36   ` Kristoffer Haugsbakk
2025-11-07 22:40     ` Elijah Newren
2025-11-17  1:01       ` Junio C Hamano
2025-11-17 19:54         ` Elijah Newren
2025-11-17 22:10           ` Junio C Hamano [this message]
2025-11-03 18:01 ` [PATCH 2/3] merge-ort: remove debugging crud Elijah Newren via GitGitGadget
2025-11-03 18:01 ` [PATCH 3/3] merge-ort: fix failing merges in special corner case Elijah Newren via GitGitGadget

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=xmqq346cia3g.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=kristofferhaugsbakk@fastmail.com \
    --cc=newren@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).