git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Joel Holdsworth <jholdsworth@nvidia.com>
Subject: jh/p4-various-fixups (was: What's cooking in git.git (Mar 2022, #07; Wed, 30))
Date: Thu, 31 Mar 2022 11:41:36 +0200	[thread overview]
Message-ID: <220331.86czi2sbg4.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqee2i50h9.fsf@gitster.g>


On Wed, Mar 30 2022, Junio C Hamano wrote:

> Also, there are a couple of "git p4" patches, for which we seem to
> totally lack reviewers.  Help is appreciated, here, too.
> [...]
> * jh/p4-various-fixups (2022-02-10) 22 commits
>  - git-p4: sort imports
>  - git-p4: seperate multiple statements onto seperate lines
>  - git-p4: move inline comments to line above
>  - git-p4: only seperate code blocks by a single empty line
>  - git-p4: compare to singletons with "is" and "is not"
>  - git-p4: normalize indentation of lines in conditionals
>  - git-p4: ensure there is a single space around all operators
>  - git-p4: ensure every comment has a single #
>  - git-p4: remove spaces between dictionary keys and colons
>  - git-p4: remove redundant backslash-continuations inside brackets
>  - git-p4: remove extraneous spaces before function arguments
>  - git-p4: place a single space after every comma
>  - git-p4: removed brackets when assigning multiple return values
>  - git-p4: remove spaces around default arguments
>  - git-p4: remove padding from lists, tuples and function arguments
>  - git-p4: sort and de-duplcate pylint disable list
>  - git-p4: remove commented code
>  - git-p4: convert descriptive class and function comments into docstrings
>  - git-p4: improve consistency of docstring formatting
>  - git-p4: indent with 4-spaces
>  - git-p4: remove unneeded semicolons from statements
>  - git-p4: add blank lines between functions and class definitions
>
>  Various cleanups to "git p4".
>
>  Needs review.
>  source: <20220210164627.279520-1-jholdsworth@nvidia.com>

The tip here lacks a Signed-Off-By, but this otherwise looks good to
me.

I don't have a setup to actually test it, but aside from the import
re-shuffling these are all purely stylistic changes.

  reply	other threads:[~2022-03-31  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31  2:17 What's cooking in git.git (Mar 2022, #07; Wed, 30) Junio C Hamano
2022-03-31  9:41 ` Ævar Arnfjörð Bjarmason [this message]
2022-04-01 14:29   ` jh/p4-various-fixups (was: What's cooking in git.git (Mar 2022, #07; Wed, 30)) Joel Holdsworth
2022-03-31  9:45 ` ab/commit-plug-leaks " Ævar Arnfjörð Bjarmason
2022-03-31  9:47 ` tk/ambiguous-fetch-refspec " Ævar Arnfjörð Bjarmason
2022-03-31  9:57 ` ab/ci-setup-simplify + ab/ci-github-workflow-markup " Ævar Arnfjörð Bjarmason
2022-03-31 14:51 ` rc/fetch-refetch " Robert Coup
2022-03-31 16:55 ` What's cooking in git.git (Mar 2022, #07; Wed, 30) Glen Choo
2022-04-03 20:05 ` Philippe Blain

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=220331.86czi2sbg4.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jholdsworth@nvidia.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.
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).