From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: libtool patches and possible release
Date: Mon, 25 Oct 2021 15:55:56 +0100 [thread overview]
Message-ID: <e91fd7eb9c529d07029e3a326e4c65cced626cfd.camel@linuxfoundation.org> (raw)
Just for info, it is possible libtool might make a release. Some of our fixes
are quite useful and would be helpful if adopted by binutils and so on so
getting them upstream would be good. As such I created a git recipe for libtool
locally, rebased our patches and then sent a curated set of 12 of them upstream:
https://lists.gnu.org/archive/html/libtool-patches/2021-10/msg00012.html
Cheers,
Richard
next reply other threads:[~2021-10-25 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 14:55 Richard Purdie [this message]
2021-10-25 16:11 ` [OE-core] libtool patches and possible release Khem Raj
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=e91fd7eb9c529d07029e3a326e4c65cced626cfd.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 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.