From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric S. Raymond" Newsgroups: gmane.emacs.devel Subject: Re: Emacs-devel Digest, Vol 46, Issue 176 Date: Mon, 31 Dec 2007 19:34:54 -0500 Organization: Eric Conspiracy Secret Labs Message-ID: <20080101003454.GF26639@thyrsus.com> References: <20071231223513.38B8D2C83E3@grelber.thyrsus.com> Reply-To: esr@thyrsus.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199149889 18695 80.91.229.12 (1 Jan 2008 01:11:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Jan 2008 01:11:29 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 01 02:11:44 2008 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 1J9VfU-0005gT-6w for ged-emacs-devel@m.gmane.org; Tue, 01 Jan 2008 02:11:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9Vf8-0006XV-84 for ged-emacs-devel@m.gmane.org; Mon, 31 Dec 2007 20:11:22 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J9Vf5-0006Wj-4j for emacs-devel@gnu.org; Mon, 31 Dec 2007 20:11:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J9Vf3-0006Uv-Pz for emacs-devel@gnu.org; Mon, 31 Dec 2007 20:11:18 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J9Vf3-0006Un-HH for emacs-devel@gnu.org; Mon, 31 Dec 2007 20:11:17 -0500 Original-Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=golux.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J9Vf3-00055d-6S for emacs-devel@gnu.org; Mon, 31 Dec 2007 20:11:17 -0500 Original-Received: by golux.thyrsus.com (Postfix, from userid 23) id 5A9DACF80C1; Mon, 31 Dec 2007 19:34:54 -0500 (EST) Content-Disposition: inline In-Reply-To: <20071231223513.38B8D2C83E3@grelber.thyrsus.com> X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.15+20070412 (2007-04-11) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:85786 Archived-At: From: Dan Nicolaescu > [I think is better to refrain from fixing the code until the byte > compiler issues are analyzed]. Noted. I was about to go in and fix them, but I'll refrain. From: Richard Stallman > If it is a problem (and other people seem to disagree with you on > this), it can't be helped. Yes, it can. I learned earlier today that you expressed an intention to hand off the Emacs maintainership after 22 was released. If you follow through on that, the new maintainer seems unlikely to have the peculiar restrictions you do. I emphatically don't want the job. But I'd like to see it pass to someone who is at least willing to use a browser. Then we could launch a web-based bug tracker on our Savannah space. That and a modern version-control system and a couple of monitor bots would be good running start. As you say, you have a lot of other things to do. Actually, you shouldn't be the Emacs lead maintainer for much the same reasons I can't be. So pick someone you think has good judgment and let it go. I strongly recommend that whoever it is should be at least fifteen years younger than either of us, if that's possible among the available candidates. Given our image problems, I think the project needs a front guy who can't possibly be dismissed as an old fart. From: Richard Stallman > An additional nice feature would be the ability to type C-c C-d and > have it show you the change set corresponding to that point in > ChangeLog. (It could do that by matching dates and approximate > matching against the log entry.) Yes. The best way to do that would actually be to synthesize history entries in a new code repository from the existing Changelog data. That actually wouldn't be very hard. Step 1: Use cvs2svn to move the CVS history to a Subversion repo. The key thing here is that it will group commits for us by date, content, and developer name. Step 2. Write a script that grovels through all Changelogs and indexes the entries by date and developer name. It can then match those to the commit groups generated in step 1 and edit them right into the commit history. Result: We now have a sequence of commit groups in the history *each one with the right block of commit data folded in*. The CVS comments and Changelogs have been merged. This is the point at which we drop the separate Changelog files, and the point at which you get your C-c C-d feature for free. Step 4. History cleanup: Now we run through the commit sequence looking for adjacent commits that should be merged, null commits, typos, and junk. We fix those. Step 5. Now we take the cleaned-up Subversion repo and lift it to whatever VCS we actually want to use. I'm willing to do this work. -- Eric S. Raymond