From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Disable emacs-diffs mails for scratch branches Date: Sat, 28 Jan 2017 21:09:10 -0500 Message-ID: References: <87sho3zewk.fsf@engster.org> <87o9yqzyq0.fsf@engster.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1485655801 1723 195.159.176.226 (29 Jan 2017 02:10:01 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 29 Jan 2017 02:10:01 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: David Engster Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 29 03:09:55 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cXewD-0007vk-HU for ged-emacs-devel@m.gmane.org; Sun, 29 Jan 2017 03:09:53 +0100 Original-Received: from localhost ([::1]:53827 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXewF-0003ft-Q9 for ged-emacs-devel@m.gmane.org; Sat, 28 Jan 2017 21:09:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50850) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXevc-0003fm-Tv for emacs-devel@gnu.org; Sat, 28 Jan 2017 21:09:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cXevZ-0007Sl-Pe for emacs-devel@gnu.org; Sat, 28 Jan 2017 21:09:16 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:37987) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cXevZ-0007Qk-I6 for emacs-devel@gnu.org; Sat, 28 Jan 2017 21:09:13 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DXLgAu3EVY/0gvq8BdGwEBAQMBAQEJAQEBgzgBAQEBAR+EW4VUnAImAZRWggiGHAQCAoIRQRMBAgEBAQEBAQFiKIRpAQQBViMQCw4mEhQYDSSIegitFItEAQEBBwIlixmEKwEBhXwFj3yKapMJhH2DFIY6kg8hAjN4Ew6FcyCGf4IuAQEB X-IPAS-Result: A0DXLgAu3EVY/0gvq8BdGwEBAQMBAQEJAQEBgzgBAQEBAR+EW4VUnAImAZRWggiGHAQCAoIRQRMBAgEBAQEBAQFiKIRpAQQBViMQCw4mEhQYDSSIegitFItEAQEBBwIlixmEKwEBhXwFj3yKapMJhH2DFIY6kg8hAjN4Ew6FcyCGf4IuAQEB X-IronPort-AV: E=Sophos;i="5.33,749,1477972800"; d="scan'208";a="290849655" Original-Received: from 192-171-47-72.cpe.pppoe.ca (HELO pastel.home) ([192.171.47.72]) by smtp.teksavvy.com with ESMTP; 28 Jan 2017 21:09:12 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 6D14065736; Sat, 28 Jan 2017 21:09:10 -0500 (EST) In-Reply-To: <87o9yqzyq0.fsf@engster.org> (David Engster's message of "Sat, 28 Jan 2017 22:00:39 +0100") X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211716 Archived-At: >>> Subject says it all. Could we please do that? I think it's pretty normal >>> for scratch-Branches being deleted and pushed anew, and for large >>> branches like cedet-merge or cedet-tests this needlessly creates >>> hundreds of mails each time. >> I agree that those 300 emails dumps are more annoying than useful. >> But FWIW, I see two problems with your suggestion: >> 1- I don't know how to do it. > We'd have to adapt the post-receive hook, or whatever else is triggering > the mails. Yes, that much I know, but I also know that we don't have direct access to it. So it depends on Savannah admins, and if I was them I wouldn't just accept random patches, since AFAIK they use an existing mail-hook and so they probably want to stay close to the upstream version to be able to incorporate future changes. So, we should figure out exactly what choices we have available. >> 2- I do find it very useful to see commits on scratch branches when >> those branches are used for gradual development (e.g. the byte-switch >> branch). > How about simply not naming those branches with the 'scratch' prefix, > then? I was under the impression that 'scratch' means "can be > force-pushed/deleted any time, don't base your work onto it". AFAICT the byte-switch does belong to scratch. Being able/allowed to force-push/delete doesn't mean that you have to do it all the time. Stefan