From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH] lint: use comments for comments, not inline docstrings
Date: Tue, 6 Oct 2015 10:27:49 -0700 [thread overview]
Message-ID: <20151006102749.0757db25.dolsen@gentoo.org> (raw)
In-Reply-To: <1444152017-2406-1-git-send-email-vapier@gentoo.org>
On Tue, 6 Oct 2015 13:20:17 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> It's uncommon to dump docstrings in the middle of code in the place of
> comments. Convert them all to standard comments.
> ---
> catalyst/base/stagebase.py | 219
> ++++++++++++++++++-------------------------
> catalyst/fileops.py | 8 +- catalyst/targets/snapshot.py
> | 8 +- 3 files changed, 99 insertions(+), 136 deletions(-)
>
>
Works for me :)
--
Brian Dolbec <dolsen>
prev parent reply other threads:[~2015-10-06 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 17:20 [gentoo-catalyst] [PATCH] lint: use comments for comments, not inline docstrings Mike Frysinger
2015-10-06 17:27 ` Brian Dolbec [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=20151006102749.0757db25.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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