Date: Fri, 1 Sep 2017 21:01:10 -0500 From: Kyle Evans <kevans91@ksu.edu> To: Shane Ambler <FreeBSD@shaneware.biz> Cc: <ports@freebsd.org>, Tobias Kortkamp <tobik@freebsd.org>, Yuri <yuri@rawbw.com> Subject: Re: Some github projects aren't fetchable using commit hash Message-ID: <CACNAnaHNav1iZ1KvutPxMBm=4hdRc13qY7Vir3UCexaZFYj2bA@mail.gmail.com> In-Reply-To: <c37d806c-f9d8-d0cb-4a55-5af9a0c5ea3b@ShaneWare.Biz> References: <aa643aff-e842-b50e-5ae5-06e6c084ed5b@rawbw.com> <1504284830.794543.1092454472.7353C7D3@webmail.messagingengine.com> <4e2b7041-6ee3-6994-437d-39de395ffca3@rawbw.com> <c37d806c-f9d8-d0cb-4a55-5af9a0c5ea3b@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 1, 2017 20:03, "Shane Ambler" <FreeBSD@shaneware.biz> wrote: Respond to github support that an abbreviated hash with multiple matches will fail. Under that condition, it may be desirable to respond with the newest of the matches rather than a not found error. To be honest, the failing seems like a little better behavior than suddenly swapping out the package I thought I was downloading with a newer version. It'd at least be a little more obvious and theoretically detectable if they respond properly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaHNav1iZ1KvutPxMBm=4hdRc13qY7Vir3UCexaZFYj2bA>