From: "dodji at seketeli dot org" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29650] "Assertion `__abg_cond__' failed." with with libabigail 2.1
Date: Tue, 11 Oct 2022 09:49:29 +0000 [thread overview]
Message-ID: <bug-29650-9487-kn0RjbyN75@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29650-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29650
--- Comment #12 from dodji at seketeli dot org ---
Hello Ben,
woodard at redhat dot com via Libabigail <libabigail@sourceware.org> a
écrit:
> Dodji can we consider a 2.1.1 fork beginning with this patch.
There is always a tag for the latest released version. The last one is
libabigail-2.1.
From that tag, if there the need for bugfix branch, I create a branch
which name is <tag>-branch, and I cherry-pick the bug fixes into that
branch.
So in this case, the branch name would be libabigail-2.1-branch.
I have just created it, with the relevant patches cherry-picked in it.
I'll be maintaining that branch for this cycle, until 2.2. I try to
avoid doing this because it's a bit more work, but when it's necessary,
well, it's necessary.
So it's available at
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/libabigail-2.1-branch.
When I roll out libabigail-2.1-2 Fedora packages, they'll be cut from
that branch.
[...]
Hello Romain,
"romain.geissler at amadeus dot com via Libabigail"
<libabigail@sourceware.org> a écrit:
[...]
> For abigail we don't use any official package, we rebuilt it from source, so I
> will chose the cherry-pick path.
[...]
Ok, so if you like, you might want to get the content of the branch
'libabigail-2.1-branch', browsable at
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/libabigail-2.1-branch,
which contains all bugfixes that will be accumulated until 2.2 is released.
[...]
Cheers.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-11 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 19:14 [Bug default/29650] New: " romain.geissler at amadeus dot com
2022-10-03 19:22 ` [Bug default/29650] " romain.geissler at amadeus dot com
2022-10-03 19:23 ` romain.geissler at amadeus dot com
2022-10-03 19:24 ` romain.geissler at amadeus dot com
2022-10-03 19:25 ` romain.geissler at amadeus dot com
2022-10-07 20:30 ` dodji at redhat dot com
2022-10-10 15:19 ` dodji at redhat dot com
2022-10-10 15:20 ` dodji at redhat dot com
2022-10-10 15:24 ` romain.geissler at amadeus dot com
2022-10-10 16:22 ` dodji at redhat dot com
2022-10-10 18:36 ` romain.geissler at amadeus dot com
2022-10-11 9:49 ` Dodji Seketeli
2022-10-10 21:23 ` woodard at redhat dot com
2022-10-11 9:49 ` dodji at seketeli dot org [this message]
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=bug-29650-9487-kn0RjbyN75@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libabigail@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).