From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier <monnier@iro.umontreal.ca> Newsgroups: gmane.emacs.devel Subject: Re: RFC: Adding BBDB to Emacs core Date: Mon, 23 Apr 2018 09:26:11 -0400 Message-ID: <jwv4lk2f46t.fsf-monnier+gmane.emacs.devel@gnu.org> References: <m3zi265o49.fsf@fitzsim.org> <ygfvacuugb7.fsf@fastmail.com> <87lgdpphmm.fsf@ericabrahamsen.net> <ygfo9il1k4i.fsf@fastmail.com> <CAM9Zgm0yQjL+tOg1cRfyfshb4oQGFMJNJ5057K58S1Fj+bJsgw@mail.gmail.com> <m21sffn2tl.fsf@newartisans.com> <87vacqcy89.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1524489926 4713 195.159.176.226 (23 Apr 2018 13:25:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 23 Apr 2018 13:25:26 +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 Mon Apr 23 15:25:22 2018 Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org> 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 <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>) id 1fAbT8-00014m-B5 for ged-emacs-devel@m.gmane.org; Mon, 23 Apr 2018 15:25:22 +0200 Original-Received: from localhost ([::1]:47138 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>) id 1fAbVD-0001tU-55 for ged-emacs-devel@m.gmane.org; Mon, 23 Apr 2018 09:27:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34416) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <ged-emacs-devel@m.gmane.org>) id 1fAbV4-0001rz-2r for emacs-devel@gnu.org; Mon, 23 Apr 2018 09:27:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <ged-emacs-devel@m.gmane.org>) id 1fAbV0-0001Tv-59 for emacs-devel@gnu.org; Mon, 23 Apr 2018 09:27:22 -0400 Original-Received: from [195.159.176.226] (port=36548 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from <ged-emacs-devel@m.gmane.org>) id 1fAbUz-0001Sl-TC for emacs-devel@gnu.org; Mon, 23 Apr 2018 09:27:18 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from <ged-emacs-devel@m.gmane.org>) id 1fAbSq-0000lP-54 for emacs-devel@gnu.org; Mon, 23 Apr 2018 15:25:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 16 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:e5U7X3J5qbPHAgxGd+p5aWmo2dE= 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." <emacs-devel.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>, <mailto:emacs-devel-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/archive/html/emacs-devel/> List-Post: <mailto:emacs-devel@gnu.org> List-Help: <mailto:emacs-devel-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>, <mailto:emacs-devel-request@gnu.org?subject=subscribe> Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org> Xref: news.gmane.org gmane.emacs.devel:224807 Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/224807> > A simple scheme could be a policy for naming development and release > branches of packages in the ELPA git repository (beyond the current > "externals" branches for individual ELPA packages), combined with tools > that allow one to access one or the other version of a package. I've had in my TODO list to add a "bleeding edge GNU ELPA" for a while and that plan is much simpler than the above: just build this alternative GNU ELPA archive from "master" by disregarding the "Version:" header. Currently, the only "official" way for users to use such a bleeding edge archive is to clone elpa.git and do "make" inside it (it takes a few more steps: check the README). Stefan