[0/1] Git.pm: add semicolon after catch statement

Message ID	20221016212236.12453-1-michael@mcclimon.org (mailing list archive)
Headers	show Return-Path: <git-owner@kernel.org> Feedback-ID: i9dc944d1:Fastmail From: Michael McClimon <michael@mcclimon.org> To: git@vger.kernel.org Cc: Michael McClimon <michael@mcclimon.org> Subject: [PATCH 0/1] Git.pm: add semicolon after catch statement Date: Sun, 16 Oct 2022 17:22:35 -0400 Message-Id: <20221016212236.12453-1-michael@mcclimon.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	Git.pm: add semicolon after catch statement \| expand [0/1] Git.pm: add semicolon after catch statement [1/1] Git.pm: add semicolon after catch statement

Message ID

20221016212236.12453-1-michael@mcclimon.org (mailing list archive)

Headers

Feedback-ID: i9dc944d1:Fastmail
From: Michael McClimon <michael@mcclimon.org>
To: git@vger.kernel.org
Cc: Michael McClimon <michael@mcclimon.org>
Subject: [PATCH 0/1] Git.pm: add semicolon after catch statement
Date: Sun, 16 Oct 2022 17:22:35 -0400
Message-Id: <20221016212236.12453-1-michael@mcclimon.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

Git.pm: add semicolon after catch statement | expand

Message

Michael McClimon Oct. 16, 2022, 9:22 p.m. UTC

When looking into a bug about Git.pm's handling of unsafe repositories [1],
I found the immediate cause of the error, which this patch fixes. This
patch doesn't do anything about the actual problem (Git.pm happily
continues to work in unsafe repositories), but it at least fixes the
runtime error.

[1] https://lore.kernel.org/git/20221011182607.f1113fff-9333-427d-ba45-741a78fa6040@korelogic.com/


Michael McClimon (1):
  Git.pm: add semicolon after catch statement

 perl/Git.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)