From: "sinny at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/19428] Write a fedabidiff utility which integrates with the Fedora build system
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <bug-19428-9487-IamEvjCfpY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19428-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19428
--- Comment #8 from Sinny Kumari <sinny at redhat dot com> ---
(In reply to Chenxiong Qi from comment #7)
> Hi Sinny,
>
> As you know that fedabipkgdiff is being under review. There are lots of work
> to do so that the first version of fedabipkgdiff can be ready to release for
> the first time. I didn't got enough time to add the case mentioned in
> comment 6, yet. I'll look into this case and other enhancement once
> fedabipkgdiff gets merged. Thanks.
Sure, it can be handled later on as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-04-29 15:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 [Bug default/19428] New: " dodji at redhat dot com
2016-01-01 0:00 ` [Bug default/19428] " cqi at redhat dot com
2016-01-01 0:00 ` Dodji Seketeli
2016-01-01 0:00 ` cqi at redhat dot com
2016-01-01 0:00 ` cqi at redhat dot com
2016-01-01 0:00 ` dodji at seketeli dot org
2016-01-01 0:00 ` sinny at redhat dot com
2016-01-01 0:00 ` cqi at redhat dot com
2016-01-01 0:00 ` cqi at redhat dot com
2016-01-01 0:00 ` [Bug default/19428] Write a fedabipkgdiff " dodji at redhat dot com
2016-01-01 0:00 ` dodji at redhat dot com
2016-01-01 0:00 ` sinny at redhat dot com [this message]
2016-01-01 0:00 ` [Bug default/19428] Write a fedabidiff " sinny at redhat 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-19428-9487-IamEvjCfpY@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).