|
From: Julian S. <se...@so...> - 2019-09-16 04:47:08
|
The signed tag 'VALGRIND_3_15_0' was created pointing to:
608cb11... Second attempt at a 3.15.0 final version.
Tagger: Julian Seward <js...@ac...>
Date: Mon Sep 16 06:46:15 2019 +0200
valgrind 3.15.0 release
|
|
From: Carl L. <ce...@us...> - 2019-09-16 14:48:58
|
Julian:
On Mon, 2019-09-16 at 04:47 +0000, Julian Seward wrote:
> The signed tag 'VALGRIND_3_15_0' was created pointing to:
>
> 608cb11... Second attempt at a 3.15.0 final version.
>
> Tagger: Julian Seward <js...@ac...>
> Date: Mon Sep 16 06:46:15 2019 +0200
>
> valgrind 3.15.0 release
Is there a tar ball somewhere we should be testing? I looked in my
mail file and this is the first I see about a new release. Just
wondering if I missed something.
Carl Love
|
|
From: Tom H. <to...@co...> - 2019-09-16 14:56:39
|
On 16/09/2019 15:48, Carl Love wrote: > On Mon, 2019-09-16 at 04:47 +0000, Julian Seward wrote: >> The signed tag 'VALGRIND_3_15_0' was created pointing to: >> >> 608cb11... Second attempt at a 3.15.0 final version. >> >> Tagger: Julian Seward <js...@ac...> >> Date: Mon Sep 16 06:46:15 2019 +0200 >> >> valgrind 3.15.0 release > > Is there a tar ball somewhere we should be testing? I looked in my > mail file and this is the first I see about a new release. Just > wondering if I missed something. It's not a new release, it's tagging the repo for the last one. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |