From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?Q?Vincent_Bela=EFche?= Newsgroups: gmane.emacs.devel Subject: RE: Addition of SES local printer functions. Date: Thu, 02 Jan 2014 21:23:55 +0100 Message-ID: <80k3eiqgis.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1388694519 27920 80.91.229.3 (2 Jan 2014 20:28:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 2 Jan 2014 20:28:39 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 02 21:28:44 2014 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 1Vyosk-0003AK-VN for ged-emacs-devel@m.gmane.org; Thu, 02 Jan 2014 21:28:43 +0100 Original-Received: from localhost ([::1]:46929 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vyosk-0007gG-Hm for ged-emacs-devel@m.gmane.org; Thu, 02 Jan 2014 15:28:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50353) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vyosd-0007Zs-El for emacs-devel@gnu.org; Thu, 02 Jan 2014 15:28:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VyosX-0007FL-Ac for emacs-devel@gnu.org; Thu, 02 Jan 2014 15:28:35 -0500 Original-Received: from smtp02.smtpout.orange.fr ([80.12.242.124]:30915 helo=smtp.smtpout.orange.fr) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VyosX-0007E3-33 for emacs-devel@gnu.org; Thu, 02 Jan 2014 15:28:29 -0500 Original-Received: from CHOUNEK ([90.32.163.58]) by mwinf5d56 with ME id 98US1n00A1FuVCy038USM6; Thu, 02 Jan 2014 21:28:27 +0100 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.12.242.124 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:167073 Archived-At: Hello Glenn, bzr status outputs the following: ----------------------------------------------------------------------- bzr status modified: doc/misc/ChangeLog doc/misc/ses.texi lisp/ChangeLog lisp/ses.el unknown: build4.log ses-local-printers.txt leim/ja-dic/ leim/leim-list.el lisp/c;c src/stamp-oldxmenu conflicts: Conflict: can't delete info because it is not empty. Not deleting. ----------------------------------------------------------------------- Concerning feature freeze exception, er... I am sorry if I did something wrong, this change has been agreed a few months ago and some advice how to implement was given by Stefan, but I hadn't any time to implement it until now. I acknowledge that this is not a _small_ change because it is involves the file format, so maybe if EMACS is in a feature freeze phase it would be wiser to delay the change or move it to some pending branch. Despite the testing that I did, there of course may be bugs involved as in any change of that sort. Anyhow, I am not aware of such "feature freeze" exception, how should I have received it --- is that some email or some message produced by bzr? Vincent. > From: rgm@gnu.org > To: vincent.b.1@hotmail.fr > Subject: Re: Addition of SES local printer functions. > Date: Thu, 2 Jan 2014 14:35:44 -0500 > CC: monnier@iro.umontreal.ca; emacs-devel@gnu.org > > Vincent Bela=EFche wrote: > > > bzr: ERROR: Conflicts detected in working tree. Use "bzr conflicts" to = list, "bzr resolve FILE" to resolve. > [...] > > bzr conflicts does not work --- probably m version of bazaar is outdate= d. > > "Does not work" is vague. Try: bzr status > > > Feedback is welcome. > > Did you receive a feature-freeze exception for this change? >