From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: no more "applied, thanks" emails from me.
Date: Tue, 3 May 2005 21:21:57 -0700 [thread overview]
Message-ID: <20050504042157.GA16103@kroah.com> (raw)
Just a short note to know that I'll probably not be sending any kind of
ACK message out to the mailing list anymore when I apply patches to my
tree. Instead, the patch submitter will get a message when it gets
applied, that contains a bunch of info about what patch it was, and
others that they have pending in my tree. (I blatently stole Andrew's
patch that also does this, and tweaked it to work in my patchflow.)
I'm doing this as I had been generating those "applied, thanks" emails
by hand, and have been getting tired of them, and I know that some
people were getting annoyed by this type of message (so much so that
they generated procmail filters to keep from having to see them.)
This new method should also be easier for me to apply more patches
faster, which is always a good thing.
And yes, sometimes these messages will escape and hit the mailing list
due to me forgetting to filter out that email address. If that happens,
sorry, my script isn't that smart...
thanks,
greg k-h
reply other threads:[~2005-05-04 4:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050504042157.GA16103@kroah.com \
--to=greg@kroah.com \
--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