From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: glitch in patchwork?
Date: Wed, 23 Nov 2022 18:42:38 -0600
Message-ID: <790d1abd-a493-6265-4b22-ace8c8f6a734@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1985511330250910133=="
List-Id: <development.lists.ipfire.org>

--===============1985511330250910133==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hey, All.

I've noticed occasional discrepancies in PATCHWORK.

For example,=20
https://patchwork.ipfire.org/project/ipfire/patch/20221108200911.11156-1-robi=
n.roevens(a)disroot.org/=20
status displays as "New", but was committed as=20
https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3De47370a167869da39c5=
962ff9f9f032d7bd995ee

This isn't a show stopper, but I thought I should point it out.

Thanks, and happy coding,
Paul

--=20
As I=E2=80=99ve gotten older, people think I=E2=80=99ve become lazy.  The tru=
th is I=E2=80=99m just being more energy efficient.


--===============1985511330250910133==--