From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK Bug 1373] Make docstrings less verbose, or reduce repeats
Date: Thu, 25 Jan 2024 19:57:56 +0000 [thread overview]
Message-ID: <bug-1373-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1373
Bug ID: 1373
Summary: Make docstrings less verbose, or reduce repeats
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Thomas mentions that testsuites files should have as few lines as possible. Of
course, we will be adding some functions which simplify the actual code, which
will aleviate this issue, but we can also look at reducing the amount of
docstring lines in DTS. He mentions if a superclass has a docstring for a
function and that function is overridden by the subclass, the docstring may not
need to be repeated in the subclass.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2985 bytes --]
reply other threads:[~2024-01-25 19:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1373-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).