From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs 26.1 release branch created Date: Sat, 16 Sep 2017 17:58:45 +0300 Message-ID: <83wp4yk7ve.fsf@gnu.org> References: <83377mls4d.fsf@gnu.org> <87bmmazt77.fsf@udel.edu> <83zi9ukbj3.fsf@gnu.org> <20170916145112.GA22458@holos.localdomain> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1505573929 26834 195.159.176.226 (16 Sep 2017 14:58:49 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 16 Sep 2017 14:58:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: Mark Oteiza Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 16 16:58:44 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 1dtEYO-0006pq-9F for ged-emacs-devel@m.gmane.org; Sat, 16 Sep 2017 16:58:44 +0200 Original-Received: from localhost ([::1]:57568 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtEYV-0005MT-Jw for ged-emacs-devel@m.gmane.org; Sat, 16 Sep 2017 10:58:51 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtEYO-0005MH-Ta for emacs-devel@gnu.org; Sat, 16 Sep 2017 10:58:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dtEYK-00018E-Ib for emacs-devel@gnu.org; Sat, 16 Sep 2017 10:58:45 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41720) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dtEYK-000187-F6; Sat, 16 Sep 2017 10:58:40 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1694 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dtEYJ-0002Ll-Iz; Sat, 16 Sep 2017 10:58:40 -0400 In-reply-to: <20170916145112.GA22458@holos.localdomain> (message from Mark Oteiza on Sat, 16 Sep 2017 10:51:12 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:218363 Archived-At: > Date: Sat, 16 Sep 2017 10:51:12 -0400 > From: Mark Oteiza > Cc: emacs-devel@gnu.org > > > > I'm working on more utilities and tests for lcms.c, where should I > > > commit those? > > > > On emacs-26, I guess. How many more utilities do you envision? > > (Tests are okay to add to emacs-26 regardless.) > > Dividing the internals of lcms-cam02-ucs into C functions, and from that > making the Lisp functions: > > lcms-xyz->jch > lcms-jch->jab > lcms-jab->jch > lcms-jch->xyz > > and adding a Lisp variable `lcms-d65-xyz' as the default whitepoint for > all the functions in lcms.c that need one. That should be two commits > if I can get all the Windows build stuff correct. That can certainly go to emacs-26. > I plan to add more, but I can wait for an emacs-26 -> master merge and > continue to work on master. If you consider the feature fairly complete for a first release, then that's fine. Otherwise we could consider adding more of your code to emacs-26, unless you think the development will take a considerable time. In general, once the first pretest is out (which will be probably a week or 2 from now), no new features should be added.