[0/2] coverity null-check fixes

Message ID	20230422135455.GA3942740@coredump.intra.peff.net (mailing list archive)
Headers	show Return-Path: <git-owner@vger.kernel.org> Date: Sat, 22 Apr 2023 09:54:55 -0400 From: Jeff King <peff@peff.net> To: git@vger.kernel.org Cc: Derrick Stolee <derrickstolee@github.com> Subject: [PATCH 0/2] coverity null-check fixes Message-ID: <20230422135455.GA3942740@coredump.intra.peff.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Precedence: bulk
Series	coverity null-check fixes \| expand [0/2] coverity null-check fixes [1/2] notes: clean up confusing NULL checks in init_notes() [2/2] fetch_bundle_uri(): drop pointless NULL check

Message ID

20230422135455.GA3942740@coredump.intra.peff.net (mailing list archive)

Headers

Date: Sat, 22 Apr 2023 09:54:55 -0400
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Derrick Stolee <derrickstolee@github.com>
Subject: [PATCH 0/2] coverity null-check fixes
Message-ID: <20230422135455.GA3942740@coredump.intra.peff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Precedence: bulk

Series

coverity null-check fixes | expand

Message

Jeff King April 22, 2023, 1:54 p.m. UTC

Here are two cases I happened to notice via Coverity. Neither produces
a user-visible bug; it's just slightly misleading code which can be
cleaned up.

The first one is ancient, but since the nearby code changed, Coverity
considered it new. :)

The second one is actually recent; I noted it already on the list, but
it was already in 'next' at that point and is now in 'master'.

-Peff