On 12/11/22 10:25, Jeremy Huddleston Sequoia wrote:
While we're on the topic of fonts, I think it would actually be great to merge
all the fonts into a single package like we did for all the protos. If we
could eliminate the configure time for ~35 packages, it would certainly help
build times
> On Dec 8, 2022, at 16:22, Peter Hutterer wrote:
>
> On Thu, Dec 08, 2022 at 12:34:33PM -0800, Alan Coopersmith wrote:
>> On 12/7/22 19:07, Peter Hutterer wrote:
>>> fwiw, I've done similar things in the past, pushing a release out just
>>> to make some internal processes easier. It's simpler
Hi
Am 08.12.22 um 02:37 schrieb Alan Coopersmith:
Normally when I go through the list of modules which have had git commits
since their last release was tagged to decide what to make new releases of,
I skip over those which only have changes that don't really affect the
installed files, such as
On Wed, Dec 07, 2022 at 05:37:27PM -0800, Alan Coopersmith wrote:
> Normally when I go through the list of modules which have had git commits
> since their last release was tagged to decide what to make new releases of,
> I skip over those which only have changes that don't really affect the
> in
On Thu, Dec 08, 2022 at 12:34:33PM -0800, Alan Coopersmith wrote:
> On 12/7/22 19:07, Peter Hutterer wrote:
> > fwiw, I've done similar things in the past, pushing a release out just
> > to make some internal processes easier. It's simpler to update to a new
> > version than shipping the one patch
On 12/7/22 19:07, Peter Hutterer wrote:
fwiw, I've done similar things in the past, pushing a release out just
to make some internal processes easier. It's simpler to update to a new
version than shipping the one patch that's actually needed (and all
other patches are just readme changes and what
On Wed, Dec 07, 2022 at 05:37:27PM -0800, Alan Coopersmith wrote:
> Normally when I go through the list of modules which have had git commits
> since their last release was tagged to decide what to make new releases of,
> I skip over those which only have changes that don't really affect the
> inst
Normally when I go through the list of modules which have had git commits
since their last release was tagged to decide what to make new releases of,
I skip over those which only have changes that don't really affect the
installed files, such as the changes for migrating to gitlab, autogen
script
