linux-kernel - Re: drm fixes for 5.3-rc9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPM=9tzo2HfwPsffe6wXGsyPhE-G+Ha7gpF=ONWUOLidxefV-Q@mail.gmail.com>
Date:   Mon, 16 Sep 2019 01:12:30 +1000
From:   Dave Airlie <airlied@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Daniel Vetter <daniel.vetter@...ll.ch>,
        LKML <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: drm fixes for 5.3-rc9

On Sun, 15 Sep 2019 at 04:58, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Thu, Sep 12, 2019 at 8:56 AM Dave Airlie <airlied@...il.com> wrote:
> >
> > Hey Linus,
> >
> > From the maintainer summit, just some last minute fixes for final,
> > details in the tag.
>
> So because my mailbox was more unruly than normal (because of same
> maintainer summit travel), I almost missed this email entirely.
>
> Why? Because you don't have the normal "git pull" anywhere in the
> email, so it doesn't trigger my search for important emails.
>
> There's a "git" in the email body, but there's not a "pull" anywhere.
> Could you add either a "please pull" or something to the email body -
> or to make things _really_ obvious, add the "[GIT PULL]" prefix to the
> subject line? Or anything, really, to whatever script or workflow you
> use to generate these?

I've been manually writing the subject lines, seems I need to fix my brain.

The reason I do that is I generate on one machine the body, and send
it via the gmail webui on whatever machine I'm using. This helps
avoids google tagging my emails as spam for generating them using
someone elses smtp servers. I should probably setup properly sending
gmail to avoid that.

Dave.