From: Thomas Monjalon <thomas@monjalon.net>
To: "Jim Holland (jimholla)" <jimholla@cisco.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Resolved Issues per release
Date: Wed, 12 Aug 2020 15:36:09 +0200 [thread overview]
Message-ID: <3190264.unCNB1XOv3@thomas> (raw)
In-Reply-To: <BL0PR11MB3201158A3404431C5EA188CCC8420@BL0PR11MB3201.namprd11.prod.outlook.com>
12/08/2020 15:32, Jim Holland (jimholla):
> The release notes at https://doc.dpdk.org/guides-20.02/rel_notes/index.html don't list the resolved issues/bugs. Is there a way to find what bugs are resolved for each dpdk release?
When looking at the git history,
every commit fixing a bug should contain a line starting with "Fixes:"
identifying the root cause.
Catching such commits will give you all details of bugs fixed.
prev parent reply other threads:[~2020-08-12 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 13:32 Jim Holland (jimholla)
2020-08-12 13:36 ` Thomas Monjalon [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=3190264.unCNB1XOv3@thomas \
--to=thomas@monjalon.net \
--cc=jimholla@cisco.com \
--cc=users@dpdk.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 NNTP newsgroup(s).