From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Sending diffs of `elpa' to the respective maintainers Date: Fri, 04 May 2012 14:08:54 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1336154952 19672 80.91.229.3 (4 May 2012 18:09:12 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 4 May 2012 18:09:12 +0000 (UTC) Cc: emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 04 20:09:11 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SQMwC-0007JJ-EO for ged-emacs-devel@m.gmane.org; Fri, 04 May 2012 20:09:04 +0200 Original-Received: from localhost ([::1]:52746 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQMwB-0007mJ-P1 for ged-emacs-devel@m.gmane.org; Fri, 04 May 2012 14:09:03 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:47954) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQMw7-0007m0-E6 for emacs-devel@gnu.org; Fri, 04 May 2012 14:09:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SQMw5-0003CA-Jw for emacs-devel@gnu.org; Fri, 04 May 2012 14:08:58 -0400 Original-Received: from ironport-out.teksavvy.com ([206.248.143.162]:27318) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQMw5-000399-F7; Fri, 04 May 2012 14:08:57 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApYIACxOgk9MCqD5/2dsb2JhbABDuCMDgQyBCIIJAQEEAVYjBQsLDiYSFBgNJIgcBbYyi2GEeQSkRYFdgwOBQA X-IronPort-AV: E=Sophos;i="4.75,391,1330923600"; d="scan'208";a="178370911" Original-Received: from 76-10-160-249.dsl.teksavvy.com (HELO ceviche.home) ([76.10.160.249]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 04 May 2012 14:08:55 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id ED21266109; Fri, 4 May 2012 14:08:54 -0400 (EDT) In-Reply-To: (Glenn Morris's message of "Fri, 04 May 2012 02:55:27 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.143.162 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:150255 Archived-At: >> It would be good to change it so it manages the maintfile itself. >> Or else couple it with a cron job that builds the maintfile. > That's easily done. Just need a thing that parses packages/*.el for > "Maintainer" or "Author" headers. I suggest doing it via cron, so that > it is not necessary to scan all packages on every commit. Need to watch > for changed addresses though, and need to undo any address munging > people might have used (or require them not to do so). No need: just rebuild the file from scratch each time. > The only issuse I see is if a new package is installed and then > a change is committed very soon after, before the maintfile gets > updated. Maybe updating the maintfile should be part of the process of > installing a new package. Maybe if the maintainer address is not found, the forwarding script should trigger a refresh of the maintainer list. > Maybe someone on this list will feel inspired to write this piece... Hopefully. >> as an error (i.e. tho I guess it would be the cron job's duty to >> detect/handle it). I.e. we need to distinguish "missing maintainer >> data" from "maintainer decided not to want it". >> I'd guess the "opt-out" would be a separate list of "opt-out email >> addresses". > I'd suggest just commenting out the relevant line in the maintainers > file. Not sure what you mean, but in any case, we can hope that noone will want to opt-out, so we may never need to solve this problem. Stefan