From: Eric Sunshine <sunshine@sunshineco.com>
To: Joel Holdsworth <jholdsworth@nvidia.com>
Cc: Git List <git@vger.kernel.org>, Luke Diamand <luke@diamand.org>,
Junio C Hamano <gitster@pobox.com>,
Tzadik Vanderhoof <tzadik.vanderhoof@gmail.com>,
Dorgon Chang <dorgonman@hotmail.com>,
Joachim Kuebart <joachim.kuebart@gmail.com>,
Daniel Levin <dendy.ua@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Ben Keene <seraphire@gmail.com>,
Andrew Oakley <andrew@adoakley.name>
Subject: Re: [PATCH 04/20] git-p4: improve consistency of docstring formatting
Date: Wed, 12 Jan 2022 14:20:36 -0500 [thread overview]
Message-ID: <CAPig+cQodfguFukatAN73Z1VvgCQqyFpUOkExvprmwhL55Zt1g@mail.gmail.com> (raw)
In-Reply-To: <20220112134635.177877-5-jholdsworth@nvidia.com>
On Wed, Jan 12, 2022 at 8:47 AM Joel Holdsworth <jholdsworth@nvidia.com> wrote:
> This patch attempts to improve the consistency of the docstrings by
> making the following changes:
>
> - Rewraps all docstrings to a 79-character column limit.
> - Adds a full stop at the end of every docstring.
> - Removes any spaces after the opening triple-quotes of all
> docstrings.
> - Sets the hanging indent of multi-line docstrings to 3-spaces.
> - Ensures that the closing triple-quotes of multi-line docstrings are
> always on a new line indented by a 3-space indent.
A couple very minor comments below... probably not worth a re-roll.
> Signed-off-by: Joel Holdsworth <jholdsworth@nvidia.com>
> ---
> diff --git a/git-p4.py b/git-p4.py
> @@ -271,20 +271,20 @@ def run_git_hook(cmd, param=[]):
> def run_hook_command(cmd, param):
> """Executes a git hook command
Missing full-stop (as described by the commit message)?
> - cmd = the command line file to be executed. This can be
> - a file that is run by OS association.
>
> - param = a list of parameters to pass to the cmd command
> + cmd -- the command line file to be executed. This can be a file that
> + is run by OS association.
> +
> + param -- a list of parameters to pass to the cmd command
These were changed from `=` to `--` (double hyphen), which is fine, but...
> @@ -715,21 +718,22 @@ def getGitTags():
> def parseDiffTreeEntry(entry):
> """Parses a single diff tree entry into its component elements.
>
> + See git-diff-tree(1) manpage for details about the format of the diff
> + output. This method returns a dictionary with the following elements:
> +
> + src_mode - The mode of the source file
> + dst_mode - The mode of the destination file
> + src_sha1 - The sha1 for the source file
> + dst_sha1 - The sha1 fr the destination file
> + status - The one letter status of the diff (i.e. 'A', 'M', 'D', etc)
> + status_score - The score for the status (applicable for 'C' and 'R'
> + statuses). This is None if there is no score.
> + src - The path for the source file.
> + dst - The path for the destination file. This is only present for
> + copy or renames. If it is not present, this is None.
... these just use `-` (single hyphen).
> + If the pattern is not matched, None is returned.
> + """
next prev parent reply other threads:[~2022-01-12 19:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 13:46 [PATCH 00/20] git-p4: Various code tidy-ups Joel Holdsworth
2022-01-12 13:46 ` [PATCH 01/20] git-p4: add blank lines between functions and class definitions Joel Holdsworth
2022-01-12 13:46 ` [PATCH 02/20] git-p4: remove unneeded semicolons from statements Joel Holdsworth
2022-01-12 13:46 ` [PATCH 03/20] git-p4: indent with 4-spaces Joel Holdsworth
2022-01-12 13:46 ` [PATCH 04/20] git-p4: improve consistency of docstring formatting Joel Holdsworth
2022-01-12 19:20 ` Eric Sunshine [this message]
2022-01-12 13:46 ` [PATCH 05/20] git-p4: convert descriptive class and function comments into docstrings Joel Holdsworth
2022-01-12 19:31 ` Eric Sunshine
2022-01-12 13:46 ` [PATCH 06/20] git-p4: remove commented code Joel Holdsworth
2022-01-12 19:33 ` Eric Sunshine
2022-01-12 13:46 ` [PATCH 07/20] git-p4: sort and de-duplcate pylint disable list Joel Holdsworth
2022-01-12 13:46 ` [PATCH 08/20] git-p4: remove padding from lists, tuples and function arguments Joel Holdsworth
2022-01-12 13:46 ` [PATCH 09/20] git-p4: remove spaces around default arguments Joel Holdsworth
2022-01-12 13:46 ` [PATCH 10/20] git-p4: place a single space after every comma Joel Holdsworth
2022-01-12 19:41 ` Eric Sunshine
2022-01-12 13:46 ` [PATCH 11/20] git-p4: remove extraneous spaces before function arguments Joel Holdsworth
2022-01-12 13:46 ` [PATCH 12/20] git-p4: remove redundant backslash-continuations inside brackets Joel Holdsworth
2022-01-12 13:46 ` [PATCH 13/20] git-p4: remove spaces between dictionary keys and colons Joel Holdsworth
2022-01-12 13:46 ` [PATCH 14/20] git-p4: ensure every comment has a single # Joel Holdsworth
2022-01-12 13:46 ` [PATCH 15/20] git-p4: ensure there is a single space around all operators Joel Holdsworth
2022-01-12 13:46 ` [PATCH 16/20] git-p4: tidied visual indented lines of conditionals Joel Holdsworth
2022-01-12 19:46 ` Eric Sunshine
2022-01-12 13:46 ` [PATCH 17/20] git-p4: compare to singletons with "is" and "is not" Joel Holdsworth
2022-01-12 19:54 ` Eric Sunshine
2022-01-12 13:46 ` [PATCH 18/20] git-p4: only seperate code blocks by a single empty line Joel Holdsworth
2022-01-12 13:46 ` [PATCH 19/20] git-p4: move inline comments to line above Joel Holdsworth
2022-01-12 13:46 ` [PATCH 20/20] git-p4: seperate multiple statements onto seperate lines Joel Holdsworth
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cQodfguFukatAN73Z1VvgCQqyFpUOkExvprmwhL55Zt1g@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=andrew@adoakley.name \
--cc=dendy.ua@gmail.com \
--cc=dorgonman@hotmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jholdsworth@nvidia.com \
--cc=joachim.kuebart@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=luke@diamand.org \
--cc=seraphire@gmail.com \
--cc=tzadik.vanderhoof@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).