Den mån 11 apr. 2022 kl 13:27 skrev Mark Phippard :
> On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf
> wrote:
> >
> > Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > > daniel.l.sahlb...@gmail.com>:
> > >
> > > > This com
On Mon, Apr 11, 2022 at 7:27 AM Mark Phippard wrote:
> On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf
> wrote:
> >
> > Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > > daniel.l.sahlb...@gmail.com>:
> > >
> > > > This c
On Sun, Apr 10, 2022 at 9:45 PM Daniel Shahaf wrote:
>
> Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> > Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> > daniel.l.sahlb...@gmail.com>:
> >
> > > This commit doesn't look correct.
> > >
> > > I executed the generate-upcomin
Daniel Sahlberg wrote on Mon, Mar 28, 2022 at 21:55:36 +0200:
> Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
> daniel.l.sahlb...@gmail.com>:
>
> > This commit doesn't look correct.
> >
> > I executed the generate-upcoming-changes-log.sh manually yesterday and it
> > created r1899244, remo
Den mån 28 mars 2022 kl 09:55 skrev Daniel Sahlberg <
daniel.l.sahlb...@gmail.com>:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was exec
Den mån 28 mars 2022 kl 13:29 skrev Nathan Hartman :
> On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg <
> daniel.l.sahlb...@gmail.com> wrote:
>
>> This commit doesn't look correct.
>>
>> I executed the generate-upcoming-changes-log.sh manually yesterday and it
>> created r1899244, removing a lot
On Mon, Mar 28, 2022 at 3:55 AM Daniel Sahlberg
wrote:
> This commit doesn't look correct.
>
> I executed the generate-upcoming-changes-log.sh manually yesterday and it
> created r1899244, removing a lot of log entries belonging to 1.14.1. This
> commit (which was executed by cron) restores them.
This commit doesn't look correct.
I executed the generate-upcoming-changes-log.sh manually yesterday and it
created r1899244, removing a lot of log entries belonging to 1.14.1. This
commit (which was executed by cron) restores them.
The crontab entry is:
[[[
# Puppet Name: Update our upcoming cha
8 matches
Mail list logo