git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Osipov, Michael (IN IT IN)" <michael.osipov@siemens.com>
Cc: git@vger.kernel.org
Subject: Re: [REGRESSION] cache.h in 2.41.0 uses undefined macros DT_*
Date: Mon, 21 Aug 2023 09:19:58 -0700	[thread overview]
Message-ID: <xmqqmsykqsep.fsf@gitster.g> (raw)
In-Reply-To: 627378df-4655-4a8a-abcb-c15ab6602101@siemens.com

I think [*1*] on June 6th fixed it, and the fix has been in 'master'
for the last 2 months, and has been in the release candidate releases
for 2.42 that have been issued in the past weeks.

Thanks.

[Reference]

*1* https://lore.kernel.org/git/20230606205935.3183276-1-asedeno@google.com

  reply	other threads:[~2023-08-21 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 12:37 [REGRESSION] cache.h in 2.41.0 uses undefined macros DT_* Osipov, Michael (IN IT IN)
2023-08-21 16:19 ` Junio C Hamano [this message]
2023-08-21 19:05   ` Osipov, Michael (IN IT IN)

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=xmqqmsykqsep.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=michael.osipov@siemens.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).