From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: RE: GIT mirror of Lisp dev sources [was: Char-folding: how can we implement matching...] Date: Wed, 2 Dec 2015 00:59:34 +0000 Message-ID: References: <8737vm2fan.fsf@red-bean.com> <0239bc4e-2682-4d73-a8ba-c5030c9fd28e@default> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2345ea6ea390525dfc9f5 X-Trace: ger.gmane.org 1449017987 15174 80.91.229.3 (2 Dec 2015 00:59:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Dec 2015 00:59:47 +0000 (UTC) Cc: emacs-devel To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 02 01:59:47 2015 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 1a3vll-0005iK-5v for ged-emacs-devel@m.gmane.org; Wed, 02 Dec 2015 01:59:41 +0100 Original-Received: from localhost ([::1]:55554 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3vlk-0007r7-Ew for ged-emacs-devel@m.gmane.org; Tue, 01 Dec 2015 19:59:40 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55017) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3vlg-0007oT-RT for emacs-devel@gnu.org; Tue, 01 Dec 2015 19:59:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3vlf-0005d7-Te for emacs-devel@gnu.org; Tue, 01 Dec 2015 19:59:36 -0500 Original-Received: from mail-lf0-x232.google.com ([2a00:1450:4010:c07::232]:33185) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3vlf-0005cx-LL for emacs-devel@gnu.org; Tue, 01 Dec 2015 19:59:35 -0500 Original-Received: by lfaz4 with SMTP id z4so31511262lfa.0 for ; Tue, 01 Dec 2015 16:59:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=aGBeclNkzzYnbjhDfBMmgpxMnLeGvH+rDPMNS1fUPLs=; b=GhMzjYbTFujSnFyYMrKuzWqHDOPnX/cbiUdBkzt2XaDtjPrHnHmhT90G/vF6EytlY0 a1/uD9z3DB+0YnhMfDRLWVJqcyuRjszP2lL1k1lGlOEQMIlBpjZHz50yU/HXoKxr613C h82ihF+jdaRI/0YTU1kzL8chmY5FTw7UuLbFd4GzLohIiVQLQ5pEAvWZNt3yvKKVlt+w Pvy3mBqB6tbIH2My+OTVS4NfY9hdvUUnBBxH9R+1mgXIs0OOYJSbIroo8LXYrdPPLCFA fkce+qbJaZt9fZIftakUmMx5e02yq+hJf7H8fmg8zkTWa6LASjf6Ps9HnxTMapWn4BuG +dcQ== X-Received: by 10.112.168.133 with SMTP id zw5mr307945lbb.95.1449017974644; Tue, 01 Dec 2015 16:59:34 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Tue, 1 Dec 2015 16:59:34 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Tue, 1 Dec 2015 16:59:34 -0800 (PST) In-Reply-To: X-Google-Sender-Auth: hv3uN1VXyTkjbH65SK6x3381qag X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c07::232 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:195728 Archived-At: --001a11c2345ea6ea390525dfc9f5 Content-Type: text/plain; charset=UTF-8 On 2 Dec 2015 12:14 am, "Drew Adams" wrote: > > > any new features should go to the master branch, while bug fixes > > and refinements should go to the emacs-25 branch (these are later > > merged onto master too). > > It's the "later" that means that master is not necessarily > up-to-date. It means that looking to master does not give > you the latest developments - until sometime "later". Yes. The sync to master would normally happen somewhat frequently. Currently it's delayed until we solve a technical issue with the new changelog system. That said, anyone who follows the development version because they want to help find bugs and issues should probably switch to the emacs-25 branch until release. As that's where we need the most polish now. --001a11c2345ea6ea390525dfc9f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 2 Dec 2015 12:14 am, "Drew Adams" <drew.adams@oracle.com> wrote:
>
> > any new features should go to the master branch, while bug fixes<= br> > > and refinements should go to the emacs-25 branch (these are later=
> > merged onto master too).
>
> It's the "later" that means that master is not necessari= ly
> up-to-date.=C2=A0 It means that looking to master does not give
> you the latest developments - until sometime "later".

Yes.

The sync to master would normally happen somewhat frequently= . Currently it's delayed until we solve a technical issue with the new = changelog system.

That said, anyone who follows the development version becaus= e they want to help find bugs and issues should probably switch to the emac= s-25 branch until release. As that's where we need the most polish now.=

--001a11c2345ea6ea390525dfc9f5--