From: David Engster <deng@randomsample.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Disable emacs-diffs mails for scratch branches
Date: Sun, 29 Jan 2017 10:59:16 +0100 [thread overview]
Message-ID: <874m0inq4r.fsf@engster.org> (raw)
In-Reply-To: <87inoy61gz.fsf@mouse> (Lars Ingebrigtsen's message of "Sun, 29 Jan 2017 03:31:40 +0100")
Lars Ingebrigtsen writes:
> David Engster <deng@randomsample.de> writes:
>
>> Subject says it all. Could we please do that?
>
> Can't you just kill-file the messages you're not interested in? I mean
> score down. That's what I do with the scratch/ branches...
Yeah sure, I do that as well. It's just that I'm kinda old-school and
think that force-pushing an amended commit shouldn't trigger 300
mails...
But since this doesn't seem to be easily changed, I guess we just live
with it.
-David
prev parent reply other threads:[~2017-01-29 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 9:56 Disable emacs-diffs mails for scratch branches David Engster
2017-01-28 15:35 ` Stefan Monnier
2017-01-28 21:00 ` David Engster
2017-01-29 2:09 ` Stefan Monnier
2017-01-29 2:31 ` Lars Ingebrigtsen
2017-01-29 9:59 ` David Engster [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m0inq4r.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).