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: [PATCH] Flymake support for C/C++ Date: Tue, 24 Oct 2017 11:44:37 -0400 Message-ID: References: <87zi8wmmhw.fsf@gmail.com> <83tvz2i2fv.fsf@gnu.org> <83r2u6i0ws.fsf@gnu.org> <87fuaivyeg.fsf@russet.org.uk> <8f681bc7-4a47-1ec7-07db-5cdb626ff22e@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1508859959 31160 195.159.176.226 (24 Oct 2017 15:45:59 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 24 Oct 2017 15:45:59 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 24 17:45:49 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 1e71OZ-00053v-M1 for ged-emacs-devel@m.gmane.org; Tue, 24 Oct 2017 17:45:35 +0200 Original-Received: from localhost ([::1]:44354 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e71Oh-0008Uk-5f for ged-emacs-devel@m.gmane.org; Tue, 24 Oct 2017 11:45:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38250) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e71O4-0008TF-Nl for emacs-devel@gnu.org; Tue, 24 Oct 2017 11:45:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e71O1-0006tc-LO for emacs-devel@gnu.org; Tue, 24 Oct 2017 11:45:04 -0400 Original-Received: from [195.159.176.226] (port=44527 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e71O1-0006so-FT for emacs-devel@gnu.org; Tue, 24 Oct 2017 11:45:01 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1e71Nl-0007l0-9p for emacs-devel@gnu.org; Tue, 24 Oct 2017 17:44:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:jvpV9heZtK0uI73Ojz1T+Rw6/Rs= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:219721 Archived-At: > Copyright assignment is a different matter: Indeed. By policy the Emacs project wants copyright assignments for the code we distribute. So in order to include flycheck in Emacs, we'd need a copyright assignment, and AFAIK this is going to be difficult to get, so by and large, the discussion to include flycheck ends here. > It's really the question of where development happens that I'm > interested in. Once we decide to include a package, there are indeed many ways we can do that: A- just include in the tarball a copy of the code freshly downloaded from upstream. B- keep a local branch tracking upstream and include that in the tarball C- keep a local branch tracking upstream and publish it in GNU ELPA D- keep a local copy in emacs.git tracking upstream E- move upstream into elpa.git F- move upstream into emacs.git G- ... I don't think (A) is a good option because it means distributing code over which we don't have any control (this said, to some extent that's what we do with the GNU ELPA version of Org, and indeed, I consider this as a problem). (C), (D), (E), and (F) are all common cases. (B) is something I was hoping we'd be doing for Emacs-26 (well, actually doing both B and C at the same time), but for some reason this has not materialized yet. Stefan