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: Emacs and the Google Summer of Code Date: Thu, 23 Apr 2009 10:35:06 -0400 Message-ID: References: <18928.5536.261692.998827@totara.tehura.co.nz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1240497413 13336 80.91.229.12 (23 Apr 2009 14:36:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 23 Apr 2009 14:36:53 +0000 (UTC) Cc: Dmitry Dzhus , emacs-devel@gnu.org To: nickrob@snap.net.nz (Nick Roberts) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 23 16:38:10 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 1Lx02e-0000mC-Uu for ged-emacs-devel@m.gmane.org; Thu, 23 Apr 2009 16:36:45 +0200 Original-Received: from localhost ([127.0.0.1]:49706 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lx01F-0008Cy-RI for ged-emacs-devel@m.gmane.org; Thu, 23 Apr 2009 10:35:17 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lx01B-0008CZ-Ne for emacs-devel@gnu.org; Thu, 23 Apr 2009 10:35:13 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lx017-0008Ac-6v for emacs-devel@gnu.org; Thu, 23 Apr 2009 10:35:13 -0400 Original-Received: from [199.232.76.173] (port=43961 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lx017-0008AZ-06 for emacs-devel@gnu.org; Thu, 23 Apr 2009 10:35:09 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:39553 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lx016-0007Nt-Kb for emacs-devel@gnu.org; Thu, 23 Apr 2009 10:35:08 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArwGADgZ8ElMCrUB/2dsb2JhbACBT85ag3UGhS4 X-IronPort-AV: E=Sophos;i="4.40,235,1238990400"; d="scan'208";a="37505214" Original-Received: from 76-10-181-1.dsl.teksavvy.com (HELO pastel.home) ([76.10.181.1]) by ironport2-out.teksavvy.com with ESMTP; 23 Apr 2009 10:35:07 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id BD5A77EFE; Thu, 23 Apr 2009 10:35:06 -0400 (EDT) In-Reply-To: <18928.5536.261692.998827@totara.tehura.co.nz> (Nick Roberts's message of "Thu, 23 Apr 2009 19:15:44 +1200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.92 (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:110432 Archived-At: > I'm pleased to say that "Emacs GDB/MI migration" was accepted as a Google > Summer of Code student project throuh the GNU Project. So I would like to > welcome Dmitry Dzhus to this list as the student of that project. I will be > acting as his mentor but I am sure that he will be able to get support from > everyone here too. Great, congratulations! > As I stated in January, I would like the resulting code would replace > gdb-ui.el after the release of Emacs 23.1. Is there any estimate for > the release date? It doesn't matter. > It would be best to commit changes to the repository, so if the > release is expected to be after the coding start date of the project > (May 23) then it would be helpful to cut a new branch where new > features for Emacs could go. Put it in a branch. If it can be put into the "branch for Emacs-23.2", that might be OK, but it can just as well go into another branch. Another good option is to put it into a Bzr or Git branch. > I know that RMS does not like this idea, as he thinks that all focus > will shift to the new branch, but I'm not sure if that's true and > there are drawbacks in not having one. Debian seem to manage with > both a testing and unstable distribution. This is a completely different issue. We're talking about a branch for a particular feature. We're not talking about opening "a new trunk". Stefan