Quoting Emil Velikov (2018-06-27 01:39:05)
> On 26 June 2018 at 16:34, Dylan Baker wrote:
>
> > I just remembered that you can set two push remotes for a single branch, so
> > I
> > think I'll add a staging/18.1 branch to master as a second remote and push
> > to
> > that as well. Do you like t
On 26 June 2018 at 16:34, Dylan Baker wrote:
> I just remembered that you can set two push remotes for a single branch, so I
> think I'll add a staging/18.1 branch to master as a second remote and push to
> that as well. Do you like that name, or would you prefer something different?
>
My initial
On Tue, 2018-06-26 at 08:34 -0700, Dylan Baker wrote:
> Quoting Juan A. Suarez Romero (2018-06-19 00:08:27)
> > On Fri, 2018-06-15 at 09:36 -0700, Dylan Baker wrote:
> > > Quoting Juan A. Suarez Romero (2018-06-15 07:26:18)
> > > > On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
> > > > > Quo
Quoting Juan A. Suarez Romero (2018-06-19 00:08:27)
> On Fri, 2018-06-15 at 09:36 -0700, Dylan Baker wrote:
> > Quoting Juan A. Suarez Romero (2018-06-15 07:26:18)
> > > On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
> > > > Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
> > > > > On Thu, J
Hi Stuart,
On 20 June 2018 at 00:10, Stuart Young wrote:
> Whichever way this goes, is it possible to have the pre-announce include a
> link to the git repo/branch in question?
>
> This way, even if it's not part of the main repo, people can easily find it
> and check out the pre-release in full.
Whichever way this goes, is it possible to have the pre-announce include a
link to the git repo/branch in question?
This way, even if it's not part of the main repo, people can easily find it
and check out the pre-release in full.
FWIW: An advantage of not requiring it to be in the main repo is t
On Mon, Jun 18, 2018 at 12:56 PM, Dylan Baker wrote:
> Quoting Juan A. Suarez Romero (2018-06-18 00:22:02)
>> On Fri, 2018-06-15 at 12:47 -0400, Ilia Mirkin wrote:
>> > On Fri, Jun 15, 2018 at 12:36 PM, Dylan Baker wrote:
>> > > I don't even understand why we make these announcements TBH. I have
Quoting Daniel Stone (2018-06-19 08:47:13)
> Hi Dylan,
> On Tue, 19 Jun 2018 at 16:42, Dylan Baker wrote:
> > Historical artifact. When I created the proposed branch we didn't have a
> > policy
> > of putting it on master instead of a personal repo, and we were discussing a
> > transition to gitl
Hi Dylan,
On Tue, 19 Jun 2018 at 16:42, Dylan Baker wrote:
> Historical artifact. When I created the proposed branch we didn't have a
> policy
> of putting it on master instead of a personal repo, and we were discussing a
> transition to gitlab. I also seem to remember that the gitlab doesn't all
Quoting Juan A. Suarez Romero (2018-06-19 00:08:27)
> On Fri, 2018-06-15 at 09:36 -0700, Dylan Baker wrote:
> > Quoting Juan A. Suarez Romero (2018-06-15 07:26:18)
> > > On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
> > > > Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
> > > > > On Thu, J
On Fri, 2018-06-15 at 09:36 -0700, Dylan Baker wrote:
> Quoting Juan A. Suarez Romero (2018-06-15 07:26:18)
> > On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
> > > Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
> > > > On Thu, Jun 14, 2018 at 6:13 PM, wrote:
> > > > > Hello list,
> > > >
On Mon, 2018-06-18 at 09:56 -0700, Dylan Baker wrote:
> Quoting Juan A. Suarez Romero (2018-06-18 00:22:02)
> > On Fri, 2018-06-15 at 12:47 -0400, Ilia Mirkin wrote:
> > > On Fri, Jun 15, 2018 at 12:36 PM, Dylan Baker wrote:
> > > > I don't even understand why we make these announcements TBH. I ha
Quoting Juan A. Suarez Romero (2018-06-18 00:22:02)
> On Fri, 2018-06-15 at 12:47 -0400, Ilia Mirkin wrote:
> > On Fri, Jun 15, 2018 at 12:36 PM, Dylan Baker wrote:
> > > I don't even understand why we make these announcements TBH. I have a
> > > public
> > > 18.1-proposed branch that I push to *
On Fri, 2018-06-15 at 12:47 -0400, Ilia Mirkin wrote:
> On Fri, Jun 15, 2018 at 12:36 PM, Dylan Baker wrote:
> > I don't even understand why we make these announcements TBH. I have a public
> > 18.1-proposed branch that I push to *every weekday*. Anyone can pull that
> > branch
> > *anytime* to g
Hi List,
Mesa 18.1.2 is now available for download.
In this release we have:
- Fixes for libatomic checks on non-arm and non-x86 platforms
- porting of additional libatomic checks to meson from autotools
- numerous radv fixes
- numerous intel fix
- several files added to the release tarball
On Fri, Jun 15, 2018 at 12:36 PM, Dylan Baker wrote:
> I don't even understand why we make these announcements TBH. I have a public
> 18.1-proposed branch that I push to *every weekday*. Anyone can pull that
> branch
> *anytime* to get the latest version. The only thing the announce email really
Quoting Juan A. Suarez Romero (2018-06-15 07:26:18)
> On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
> > Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
> > > On Thu, Jun 14, 2018 at 6:13 PM, wrote:
> > > > Hello list,
> > > >
> > > > The candidate for the Mesa 18.1.2 is now available. Cu
On 15 June 2018 at 15:26, Juan A. Suarez Romero wrote:
> On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
>> Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
>> > On Thu, Jun 14, 2018 at 6:13 PM, wrote:
>> > > Hello list,
>> > >
>> > > The candidate for the Mesa 18.1.2 is now available. Curr
On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote:
> Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
> > On Thu, Jun 14, 2018 at 6:13 PM, wrote:
> > > Hello list,
> > >
> > > The candidate for the Mesa 18.1.2 is now available. Currently we have:
> > > - 42 queued
> > > - 6 nominated (outsta
Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49)
> On Thu, Jun 14, 2018 at 6:13 PM, wrote:
> > Hello list,
> >
> > The candidate for the Mesa 18.1.2 is now available. Currently we have:
> > - 42 queued
> > - 6 nominated (outstanding)
> > - and 0 rejected patches
> >
> > Notable changes in this
On Thu, Jun 14, 2018 at 6:13 PM, wrote:
> Hello list,
>
> The candidate for the Mesa 18.1.2 is now available. Currently we have:
> - 42 queued
> - 6 nominated (outstanding)
> - and 0 rejected patches
>
> Notable changes in this release:
> - numerous fixes for radv
> - libatomic checks for meso
Hello list,
The candidate for the Mesa 18.1.2 is now available. Currently we have:
- 42 queued
- 6 nominated (outstanding)
- and 0 rejected patches
Notable changes in this release:
- numerous fixes for radv
- libatomic checks for meson, as well as fixing coverage for less common (not
arm or
22 matches
Mail list logo
