From: "Eric F (iEFdev)" <eric@iefdev.se>
To: Markus Mayer <code@mmayer.net>
Cc: CGit list <cgit@lists.zx2c4.com>
Subject: Re: cgit-1.2.3: Undefined symbols for architecture x86_64: "_memrchr"
Date: Sat, 8 Aug 2020 20:28:18 +0200 [thread overview]
Message-ID: <9de05189-9247-76bb-3633-e8b6ba3e45ad@iefdev.se> (raw)
In-Reply-To: <CANEuBv7_TrihNXLNupfoJTxS-jTKYwgGdWo57hNgdTV=QFeN=g@mail.gmail.com>
Hi Markus,
Thank you so much for the fast response – and thanks for the patch you sent in
the other mail:
- https://lists.zx2c4.com/pipermail/cgit/2020-August/004506.html
I'm all about to hit the bed now, but I'll try this one soon and will report
back if it worked here as well.
Thanks again!
Best,
· Eric
On 8/8/20 20:07 , Markus Mayer wrote:
> I submitted a patch for this a month or two ago, but it doesn't seem
> to be making it to the mailing list for reasons unknown. I even tried
> sending it twice. Do dice.
>
> Regards,
> -Markus
next prev parent reply other threads:[~2020-08-08 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 17:22 Eric F (iEFdev)
2020-08-08 18:07 ` Markus Mayer
2020-08-08 18:28 ` Eric F (iEFdev) [this message]
2020-08-09 7:04 ` Eric F (iEFdev)
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=9de05189-9247-76bb-3633-e8b6ba3e45ad@iefdev.se \
--to=eric@iefdev.se \
--cc=cgit@lists.zx2c4.com \
--cc=code@mmayer.net \
/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).