From: "Farid Zakaria" <farid.m.zakaria@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>,
"Farid Zakaria" <farid.m.zakaria@gmail.com>
Cc: "Phillip Wood" <phillip.wood123@gmail.com>, <git@vger.kernel.org>,
"Phillip Wood" <phillip.wood@dunelm.org.uk>,
"Elijah Newren" <newren@gmail.com>,
"Patrick Steinhardt" <ps@pks.im>
Subject: Re: [PATCH v3] sequencer: honor --empty when a fixup!/squash! empties its target
Date: Fri, 07 Aug 2026 15:26:57 -0700 [thread overview]
Message-ID: <DKJ2CZKJC6P0.VHLMCUDH6Z44@gmail.com> (raw)
In-Reply-To: <xmqq8q6jhtws.fsf@gitster.g>
On Thu Aug 6, 2026 at 1:32 PM PDT, Junio C Hamano wrote:
> "Farid Zakaria" <farid.m.zakaria@gmail.com> writes:
>
>> Let me know if you have any more comments. I suspect not much will
>> changes logic-wise once I rebase it onto 'next'.
>>
>> For clarity, is the f85a7e6620 commit the 'next' branch ? I would have
>> thought to just rebase ontop of 'next' and I'm a bit confused with this
>> commit hash.
>>
>> If there is anything else I should be aware of, I would appreciate a CC
>> if you can remember :)
>
> It has been quite a while since you received a reply from Phillip to
> the quoted message above. Has there been any progress to share?
>
> Thanks.
Hi Junio,
Sorry I let this slip. I was waiting for the work to be accepted to
avoid rebasing on top of a moving target -- I am still a little new to
mailing list workflow & I have been using b4 (recommended from Linux).
I will pick this up again soon.
next prev parent reply other threads:[~2026-08-07 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 0:38 [PATCH v3] sequencer: honor --empty when a fixup!/squash! empties its target Farid Zakaria
2026-07-12 5:01 ` Junio C Hamano
2026-07-13 13:18 ` Phillip Wood
2026-07-13 16:30 ` Farid Zakaria
2026-07-15 15:44 ` Phillip Wood
2026-08-06 20:32 ` Junio C Hamano
2026-08-07 22:26 ` Farid Zakaria [this message]
2026-07-15 15:30 ` Phillip Wood
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=DKJ2CZKJC6P0.VHLMCUDH6Z44@gmail.com \
--to=farid.m.zakaria@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/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.