From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: allout update checkin questions Date: Wed, 18 Feb 2009 21:58:23 -0500 Message-ID: References: <2cd46e7f0902181717h2b592a32wa825c2ca8e6af598@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1235012323 32541 80.91.229.12 (19 Feb 2009 02:58:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Feb 2009 02:58:43 +0000 (UTC) Cc: Emacs Developers To: ken manheimer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 19 03:59:58 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LZz8m-0001dl-Tp for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2009 03:59:57 +0100 Original-Received: from localhost ([127.0.0.1]:43601 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZz7S-0007Gw-Ma for ged-emacs-devel@m.gmane.org; Wed, 18 Feb 2009 21:58:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LZz7N-0007Gh-By for emacs-devel@gnu.org; Wed, 18 Feb 2009 21:58:29 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LZz7L-0007GV-07 for emacs-devel@gnu.org; Wed, 18 Feb 2009 21:58:28 -0500 Original-Received: from [199.232.76.173] (port=35057 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZz7K-0007GS-Pw for emacs-devel@gnu.org; Wed, 18 Feb 2009 21:58:26 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:14029 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LZz7K-0003Zl-Dk for emacs-devel@gnu.org; Wed, 18 Feb 2009 21:58:26 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq0EAM5ZnElMCpTK/2dsb2JhbACBbtIlhBMGgzw X-IronPort-AV: E=Sophos;i="4.38,231,1233550800"; d="scan'208";a="34067702" Original-Received: from 76-10-148-202.dsl.teksavvy.com (HELO pastel.home) ([76.10.148.202]) by ironport2-out.teksavvy.com with ESMTP; 18 Feb 2009 21:58:24 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id C05A68442; Wed, 18 Feb 2009 21:58:23 -0500 (EST) In-Reply-To: <2cd46e7f0902181717h2b592a32wa825c2ca8e6af598@mail.gmail.com> (ken manheimer's message of "Wed, 18 Feb 2009 20:17:47 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.90 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:109205 Archived-At: > First, I'm frankly clueless about use of checkin tags and branches in > the emacs project. i would like my current batch of revisions to be > included in the next emacs point release. is there a particular > branch or tag i should be using on my checkin? in general, where > should i be looking to see info for elisp developers about the current > emacs checkin branching/release practices? There is no branch yet for the code "after 23.1". I suggest you create a branch on the allout.el file. Most CVS primers should be able to tell you how to do that. E.g. something like: cvs tag ALLOUT_WORK_BASE allout.el cvs tag -b ALLOUT_WORK allout.el will create the branch (together with a tag that keeps track of the base of the branch, which you can move if/when you sync your code with the trunk code) and then cvs update -r ALLOUT_WORK allout.el will get you the ALLOUT_WORK version of allout.el and commits on it will go to that branch. > also, i notice that the currently checked in allout version excludes > some small xemacs compatability provisions, and am wondering why that > was done. specifically, there were numerous: > > (local-variable-p varname (current-buffer)) > > that were replaced by: > > (local-variable-p varname) Sounds like mistakes. Feel free to change the code to be more compatible with XEmacs. > I have let XEmacs compatibility slide, but in general see no reason to > deliberately introduce incompatibility. Neither do I. Stefan