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: Re: allout update checkin questions Date: Thu, 19 Feb 2009 13:58:11 -0500 Message-ID: <2cd46e7f0902191058ua0850e1wa27ec1cc99fef12f@mail.gmail.com> References: <2cd46e7f0902181717h2b592a32wa825c2ca8e6af598@mail.gmail.com> <2cd46e7f0902191043s34a42f0eo617d7d039b97b52e@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 1235069968 22672 80.91.229.12 (19 Feb 2009 18:59:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Feb 2009 18:59:28 +0000 (UTC) Cc: Emacs Developers To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 19 20:00:42 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 1LaE8P-0004Ky-Q2 for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2009 20:00:34 +0100 Original-Received: from localhost ([127.0.0.1]:42819 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LaE75-0002KA-CS for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2009 13:59:11 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LaE6A-0001l6-3R for emacs-devel@gnu.org; Thu, 19 Feb 2009 13:58:14 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LaE69-0001kb-KW for emacs-devel@gnu.org; Thu, 19 Feb 2009 13:58:13 -0500 Original-Received: from [199.232.76.173] (port=33779 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LaE69-0001kT-7B for emacs-devel@gnu.org; Thu, 19 Feb 2009 13:58:13 -0500 Original-Received: from mail-bw0-f160.google.com ([209.85.218.160]:51167) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LaE68-00082h-LN for emacs-devel@gnu.org; Thu, 19 Feb 2009 13:58:12 -0500 Original-Received: by bwz4 with SMTP id 4so1554149bwz.18 for ; Thu, 19 Feb 2009 10:58:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=N5enrBc2dYxjz9v2NY4ffKakl6rtRYqFB/OekEe8WEI=; b=hl5zXlHJ9tnkT0kJaTuoMA/N/6miYFRiQRV/AKSmOzUpcY/tI3XanNWYrOgppwmBHL RcjFausEMgzZRqV140nHDGtXy5N7PNxB/x9e19usjKb1rrnQFbu352wUhRGNz2xqWZUm tc9NlxnAowGL23+5M9cbYR8D+/foX79OlzuKo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TzA27v98T67jKou2mMFQbEMPVYb0pSFNML5dlcGxB1AWYRIdfty+1ZMhEloo56s3qk LdBMzQxX02b+CC7CapVV4PNKsoI7HHRbhd5CKsBnv0PoF6yp1hQKyF+6Vpg9y8XyHHZv uCW3o5z5XdTLGIPm7uOQ+PkCZE7P8vi45QvfM= Original-Received: by 10.181.226.2 with SMTP id d2mr69835bkr.15.1235069891442; Thu, 19 Feb 2009 10:58:11 -0800 (PST) In-Reply-To: <2cd46e7f0902191043s34a42f0eo617d7d039b97b52e@mail.gmail.com> 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:109225 Archived-At: (i should add, regardless of checkin privileges, i've searched on various occasions for info about which branch or tag to use when checking out the development emacs, and always wind up just guessing at HEAD and/or what a particular release identifier might be. i may well be missing something obvious, but it would have helped me to have this kind of developer guidance / procedural descriptions linked to the savannah project home page, and i expect that others would find it useful, too.) On Thu, Feb 19, 2009 at 1:43 PM, ken manheimer wrote: > On Wed, Feb 18, 2009 at 9:58 PM, Stefan Monnier > wrote: > >> > 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. > > sorry, i was unclear. i'm well acquainted with using CVS. what i'm > clueless about are the emacs checkin and release protocols, and i have > completely failed to find guidance docs. > > specifically, i'd like to know where to look for things like what the > current development branch is, what to do to nominate something for > release, who to talk to about questions and concerns, etc. a while > back i spent some time looking for developer guidance documents on > savannah, but that didn't help at all - maybe i missed something, or > maybe it's been added since. is there a canonical collection of > instructions, or even some generally used guidance docs? > >> 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. > > i use my own CVS repository for my personal development. i can > checkin changes to a gnu repository branch, tagged as you suggest, > when i release my changes from my own repository to the gnu one. > >> > 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. > > great! > > thanks! > -- > ken > http://myriadicity.net > -- ken http://myriadicity.net