linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm fixes for 5.3-rc9
Date: Sun, 15 Sep 2019 09:26:24 -0700	[thread overview]
Message-ID: <CAHk-=whEvtTBXx7No=UMg9gXtqm6gzt3bT960UpoLOctokRB6w@mail.gmail.com> (raw)
In-Reply-To: <CAPM=9tzo2HfwPsffe6wXGsyPhE-G+Ha7gpF=ONWUOLidxefV-Q@mail.gmail.com>

On Sun, Sep 15, 2019 at 8:12 AM Dave Airlie <airlied@gmail.com> wrote:
>
> I've been manually writing the subject lines, seems I need to fix my brain.

Note that my "find git pull requests" logic doesn't need it in the
subject line at all, so if you just change whatever script you use to
generate the email body to have an additional "pull" in there
somewhere, that's perfectly workable too.

> 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.

Don't worry too much about it too much.

I _do_ try to always read all my email, it's just that I find things
faster that match that pattern.

And I don't think I've actually lost one of your pull requests (knock
wood), they might just end up delayed a bit.

That said - having "[GIT PULL]" in the subject line is how the
pr-tracker-bot finds the emails too, so if you do the subject line
thing, you'll not only trigger my search term, you'll also get the
nice notifications from the bot when I've pushed out my merge.

              Linus

      reply	other threads:[~2019-09-15 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12 15:56 drm fixes for 5.3-rc9 Dave Airlie
2019-09-14 18:57 ` Linus Torvalds
2019-09-15 15:12   ` Dave Airlie
2019-09-15 16:26     ` Linus Torvalds [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHk-=whEvtTBXx7No=UMg9gXtqm6gzt3bT960UpoLOctokRB6w@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).