From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2023, #01; Tue, 4)
Date: Wed, 05 Apr 2023 15:47:50 -0700 [thread overview]
Message-ID: <xmqqa5zmrlnt.fsf@gitster.g> (raw)
In-Reply-To: CAMP44s1ePrbxQc3KzU8A2Z-ZMXTaJHyt5hh9JsY337kd=OvOCw@mail.gmail.com
Felipe Contreras <felipe.contreras@gmail.com> writes:
> Any reason why this patch to remove a workaround only needed for ~2005
> software wasn't picked?
>
> https://lore.kernel.org/git/20230322000815.132128-1-felipe.contreras@gmail.com/
I did not pick it up because I did not see it. It seems Todd gave
an ack on it---I will queue it and merge it to 'next' soonish.
Thanks for a ping.
next prev parent reply other threads:[~2023-04-05 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 0:14 What's cooking in git.git (Apr 2023, #01; Tue, 4) Junio C Hamano
2023-04-05 15:07 ` Felipe Contreras
2023-04-05 22:47 ` Junio C Hamano [this message]
2023-04-06 2:31 ` Felipe Contreras
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=xmqqa5zmrlnt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/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).