Re: forge package sparsersb
Michele Martone via Discussion List for GNU Octave Maintainers <[email protected]> Tue, 19 Oct 2021 07:43:18 +0000
| Newsgroups | gmane.comp.gnu.octave.maintainers |
|---|---|
| Message-ID | <20211019074318.GA14167@localhost> |
--===============2136540631437980351== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 20211019@08:25, Andreas Weber wrote: > Am 19.10.21 um 07:22 schrieb Montgomery-Smith, Stephen: > > In the last few days, someone rerolled sparsersb, including some > > tangible changes, without updating the version number. >=20 > Are you talking about https://sourceforge.net/p/octave/sparsersb/ci/67a14= d968d2db3ffe34474e6be1c7a2d164ad416/ > ? >=20 > Looks fine for me, can you provide a link and clarify what you expect to > see? >=20 > Thank you, Andy One month ago we did a reroll: https://sourceforge.net/p/octave/package-releases/453/#c8cc/27be and the tag adjustment commit pointed out by Andy came a few days later, but it matches the release. --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQdu1Va6jWbiq8Ma4jg5mnI7xJYuAUCYW53EwAKCRDg5mnI7xJY uF0/AJ9QorEUfRjONATSrI200HrZfz4xzQCfduj0Ry8GcxCBTyVpi/sSLNuKkLA= =+TJH -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- --===============2136540631437980351== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline Ci0tLS0tLS0tLS0KV2UgYXJlIHRyYW5zaXRpb25pbmcgdG8gYSB3ZWIgYmFzZWQgZm9ydW0KZm9y IG1haW50YWluZXIgZGlzY3Vzc2lvbnMgYXQKaHR0cHM6Ly9vY3RhdmUuZGlzY291cnNlLmdyb3Vw L2MvbWFpbnRhaW5lcnM= --===============2136540631437980351==--