From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ken manheimer Newsgroups: gmane.emacs.devel Subject: allout update checkin questions Date: Wed, 18 Feb 2009 20:17:47 -0500 Message-ID: <2cd46e7f0902181717h2b592a32wa825c2ca8e6af598@mail.gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1235006284 19663 80.91.229.12 (19 Feb 2009 01:18:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Feb 2009 01:18:04 +0000 (UTC) To: Emacs Developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 19 02:19:19 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 1LZxZP-000311-7g for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2009 02:19:19 +0100 Original-Received: from localhost ([127.0.0.1]:41291 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZxY4-00051Y-Sm for ged-emacs-devel@m.gmane.org; Wed, 18 Feb 2009 20:17:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LZxXz-00050y-MU for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:17:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LZxXy-00050Z-Or for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:17:50 -0500 Original-Received: from [199.232.76.173] (port=43559 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LZxXy-00050W-Jm for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:17:50 -0500 Original-Received: from fg-out-1718.google.com ([72.14.220.153]:7525) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LZxXy-0004Oh-8Z for emacs-devel@gnu.org; Wed, 18 Feb 2009 20:17:50 -0500 Original-Received: by fg-out-1718.google.com with SMTP id l27so945488fgb.30 for ; Wed, 18 Feb 2009 17:17:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=3+OY0DNIs+aFBJkesvYsKBWtMdGlf1/MwGll/MTFoHo=; b=EJq4HZeLE56foXRp/wU4HvSDZ6/nsTLxnRNY6b2iGj6uHTPeWbmeNfUP/yvt4cGTRx /Sku211bfvQXXN+VDoNV3UwYZ48HJ2mcz5jfFMuaaK1Pf+uz2oGYbo5vVVidtFFE1GQC syBMXGuJHxXwcoW/ZfS7Of6VhoRzkqGWLOFi4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Gg/IWR28dyDcDxkRNY6/Ld8KGJm/G3vI11qx6bsx11FhM8/MDO+K7QPh6Q3yKOowkG OJOGaGZL0JU7QbthvaXIyEyB0qibDfQ6bCEJHTN8Uy3S/P9uOu0JpOPSUM0KocQOPYAL SKT4ScShQ4VtB3mwiK+BsPf4xb4Fpu2qAI3KQ= Original-Received: by 10.103.117.9 with SMTP id u9mr24545mum.55.1235006267996; Wed, 18 Feb 2009 17:17:47 -0800 (PST) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:109203 Archived-At: hi, all! i'm working on a few allout changes and have a few incidental procedural questions. 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? 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) in (i think, current) xemacs, the buffer argument is not optional, so this specifically introduced incompatibilities, for no purpose i can see. i would like to reestablish that provision in the allout version i checkin. is this somehow contrary to policy/practice? i have let xemacs compatibility slide, but in general see no reason to deliberately introduce incompatibility. thanks! -- ken manheimer http://myriadicity.net