Re: RISC-V Vector patch

--===============2494534775103785030==
Content-Type: multipart/alternative; boundary="000000000000a1554f05fd13b438"

--000000000000a1554f05fd13b438
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 1, 2023 at 12:39=E2=80=AFAM Drago=C8=99 Tiselice via png-mng-im=
plement <
png-mng-implement-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> wrote:

> Thank you for the advice. I have reached out to Cosmin on Gmail without
> getting a reply back.
>
> Also, GitHub seems to be behind/unmaintained compared to SourceForge.
>

All the github repos and sourceforge (
https://sourceforge.net/projects/libpng/) seem to be in step; the last
change on sourceforge was on 12 February 2023 and the same goes for
libpng16 on github.com (https://github.com/glennrp/libpng).  "master" and
"tmp/develop" are up-to-date with libpng16.  I believe "master" and
"tmp/develop" are identical to libpng16 on github,com; commits 0/0
ahead/behind.

This is the way it should be; the two "master" branches on sourceforge and
github should both point to the current major release (libpng16).  I never
used sourceforge (well, not after the indemnification issue) and all
development was done on github; it is likely that from time to time the
branches on github pointed to something that was somewhat unstable.  Only
tagged revisions are fully tested.  "tmp/develop" is new and, I assume, was
created to avoid that.

I won't discuss the specific merge request here (discussions should go in a
"pull" request on github) beyond pointing out:

https://github.com/mschlaegl/libpng_rvv-doc
https://github.com/mschlaegl/libpng_rvv
https://github.com/glennrp/libpng/pull/405

Plus observing that I suspect third party testing of these (mschlaegl)
changes (preferably synced up to date with glennrp/libpng16) would
certainly help validate them.

--000000000000a1554f05fd13b438
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jun 1, 2023 at 12:39=E2=80=AFAM D=
rago=C8=99 Tiselice via png-mng-implement &lt;<a href=3D"mailto:png-mng-imp=
[email protected]">png-mng-implement-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org</a>&g=
t; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div dir=3D"ltr">Thank you for the advice. I have reac=
hed out to Cosmin on Gmail without getting a reply back.<div><br></div><div=
>Also, GitHub seems to be behind/unmaintained compared to SourceForge.</div=
></div></blockquote><div><br></div><div>All the github repos and sourceforg=
e (<a href=3D"https://sourceforge.net/projects/libpng/">https://sourceforge=
.net/projects/libpng/</a>) seem to be in step; the last change on sourcefor=
ge was on 12 February 2023 and the same goes for libpng16 on <a href=3D"htt=
p://github.com">github.com</a> (<a href=3D"https://github.com/glennrp/libpn=
g">https://github.com/glennrp/libpng</a>).=C2=A0 &quot;master&quot; and &qu=
ot;tmp/develop&quot; are up-to-date with libpng16.=C2=A0 I believe &quot;ma=
ster&quot; and &quot;tmp/develop&quot; are identical to libpng16 on github,=
com; commits 0/0 ahead/behind.</div><div><br></div><div>This is the way it =
should be; the two &quot;master&quot; branches on sourceforge and github sh=
ould both point to the current major release (libpng16).=C2=A0 I never used=
 sourceforge (well, not after the indemnification issue) and all developmen=
t was done on github; it is likely that from time to time the branches on g=
ithub pointed to something that was somewhat unstable.=C2=A0 Only tagged re=
visions are fully tested.=C2=A0 &quot;tmp/develop&quot; is new and, I assum=
e, was created to avoid that.</div><div><br></div><div>I won&#39;t discuss =
the specific merge request here (discussions should go in a &quot;pull&quot=
; request on github) beyond pointing out:</div><div><br></div><div><a href=
=3D"https://github.com/mschlaegl/libpng_rvv-doc">https://github.com/mschlae=
gl/libpng_rvv-doc</a><br></div><div><a href=3D"https://github.com/mschlaegl=
/libpng_rvv">https://github.com/mschlaegl/libpng_rvv</a><br></div><div><a h=
ref=3D"https://github.com/glennrp/libpng/pull/405">https://github.com/glenn=
rp/libpng/pull/405</a><br></div><div><br></div><div>Plus observing that I s=
uspect third party testing of these (mschlaegl) changes (preferably synced =
up to date with glennrp/libpng16) would certainly help validate them.</div>=
<div><br></div></div></div>

--000000000000a1554f05fd13b438--


--===============2494534775103785030==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============2494534775103785030==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
png-mng-implement mailing list
png-mng-implement-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

--===============2494534775103785030==--