From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bill Wohler Newsgroups: gmane.emacs.devel,gmane.mail.mh-e.devel Subject: Re: The MH-E repository Date: Tue, 31 May 2005 10:09:41 -0700 Organization: Newt Software Message-ID: <13139.1117559381@olgas.newt.com> References: <25625.1117492799@olgas.newt.com> <87is0z5yyv.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1117559429 25815 80.91.229.2 (31 May 2005 17:10:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 May 2005 17:10:29 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 31 19:10:26 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DdAFD-00039w-BZ for ged-emacs-devel@m.gmane.org; Tue, 31 May 2005 19:09:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DdAKK-0006sH-NF for ged-emacs-devel@m.gmane.org; Tue, 31 May 2005 13:14:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DdAJr-0006hz-BQ for emacs-devel@gnu.org; Tue, 31 May 2005 13:14:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DdAJp-0006gr-6G for emacs-devel@gnu.org; Tue, 31 May 2005 13:14:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DdAJo-0006el-N8 for emacs-devel@gnu.org; Tue, 31 May 2005 13:14:20 -0400 Original-Received: from [207.69.195.71] (helo=pop-siberian.atl.sa.earthlink.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DdAHI-0003ce-RY for emacs-devel@gnu.org; Tue, 31 May 2005 13:11:45 -0400 Original-Received: from h-68-165-7-193.snvacaid.dynamic.covad.net ([68.165.7.193] helo=olgas.newt.com) by pop-siberian.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DdAFU-00001i-00; Tue, 31 May 2005 13:09:52 -0400 Original-Received: by olgas.newt.com (Postfix, from userid 1000) id 56BD516F9F; Tue, 31 May 2005 10:09:41 -0700 (PDT) Original-Received: from olgas.newt.com (localhost [127.0.0.1]) by olgas.newt.com (Postfix) with ESMTP id 4FFA116F9E; Tue, 31 May 2005 10:09:41 -0700 (PDT) Original-To: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org In-Reply-To: Stefan Monnier's message of Tue, 31 May 2005 09:08:47 EDT. <87is0z5yyv.fsf-monnier+emacs@gnu.org> X-Mailer: MH-E 7.83+cvs; nmh 1.1; GNU Emacs 21.4.1 X-Image-URL: http://www.newt.com/wohler/images/bill-diving.png Mail-Followup-To: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org 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:37948 gmane.mail.mh-e.devel:10447 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37948 Stefan Monnier wrote: > - RMS doesn't automatically give write access to people who signed papers. Not having write access would be a show-stopper. Question to MH-E developers: which of you know that you don't have write access, or aren't sure? > - Maybe you could automate the syncing some more and do it more frequently. > > - Take a look at the way Gnus's code is synced. The use of Arch for that is > key. Tell me more. Is there a document like http://mh-e.sourceforge.net/doc/devguide.html that explains the process? I'm not familiar with Arch. Are you talking about http://www.gnu.org/software/gnu-arch/? How often do you sync? Do you clone the CVS check-ins including log messages? It looks like the answer is yes and no. Looking at the Emacs log, it appears that many of the messages are "Merge from..." although I see some similarity with the log messages in the Gnus CVS repository. I'm currently syncing at MH-E releases (about 4/year) with Emacs cvs logs like "Upgraded to MH-E version 7.84. See etc/MH-E-NEWS and lisp/mh-e/ChangeLog for details." My MH-E CVS logs are very similar to the Gnus CVS logs (as I look at the Gnus CVS log). Kim F. Storm wrote: > How many developers are involved? > > Have they signed papers for MH-E only, or general past/future changes > for emacs as a whole? Mark answered this nicely. > > contrib, debian, htdocs, xemacs modules. These would remain on > > SourceForge. > > Why? I think you might not understand what I'm talking about. I'm not talking about moving the SourceForge MH-E project to Savannah, I'm merely talking about not having two separate CVS repositories for the lisp/mh-e directory. Miles Bader wrote: > What _advantage_ is there to having [MH-E maintenance files] be included? Less up-front effort modifying scripts with a different layout. There wouldn't be any advantage to the Emacs project as a whole, so I'm expecting that I will be keeping them external from emacs/lisp/mh-e. > BTW, I personally would prefer it if the non-lisp files would go in > "proper" locations, eg. image files in etc/images, etc. I think Gnus > is a very good model to follow on this... I agree. The MH-E package shares images with the mail and toolbar packages. If you were developing MH-E with a non-CVS Emacs, then you would have to be careful about putting lisp/mail at the end of your load-path so you don't get the wrong version of the mail elisp files. If I were to make the requisite changes in MH-E, would someone be willing to make the changes to these other packages? -- Bill Wohler http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane.