From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/21485] problems compiling with clang
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <bug-21485-9487-GvPVChxVRb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21485-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21485
--- Comment #7 from dodji at redhat dot com ---
Comment on attachment 10047
--> https://sourceware.org/bugzilla/attachment.cgi?id=10047
address some of the problems
I have committed and pushed this to the master branch into commit
https://sourceware.org/git/gitweb.cgi?p=libabigail.git;a=commit;h=b8a629f4a18cd132a600e67677706a1f44cb8024.
I have amended the commit to remove the change that was undone by the next
patch. I have also added a change log to it, to make it comply with the commit
log guidelines of the project at
https://sourceware.org/git/gitweb.cgi?p=libabigail.git;a=blob_plain;f=COMMIT-LOG-GUIDELINES
Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-06-03 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 [Bug default/21485] New: " woodard at redhat dot com
2017-01-01 0:00 ` [Bug default/21485] " woodard at redhat dot com
2017-01-01 0:00 ` dodji at redhat dot com
2017-01-01 0:00 ` woodard at redhat dot com
2017-01-01 0:00 ` dodji at redhat dot com
2017-01-01 0:00 ` jwakely.gcc at gmail dot com
2017-01-01 0:00 ` woodard at redhat dot com
2017-01-01 0:00 ` jwakely.gcc at gmail dot com
2017-01-01 0:00 ` dodji at redhat dot com [this message]
2017-01-01 0:00 ` woodard at redhat dot com
2020-11-12 13:40 ` maennich at android dot com
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-21485-9487-GvPVChxVRb@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).