From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/69775 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: synchronizing with Emacs, take two Date: Thu, 1 Jul 2010 08:59:14 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87tyoj4825.fsf@lifelogs.com> References: <87zl07ynxi.fsf@gate450.dyndns.org> <87y6dw6w60.fsf@lifelogs.com> <87d3v86vof.fsf_-_@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: dough.gmane.org 1277992831 11524 80.91.229.12 (1 Jul 2010 14:00:31 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 1 Jul 2010 14:00:31 +0000 (UTC) Cc: To: Katsumi Yamaoka Original-X-From: ding-owner+M18165@lists.math.uh.edu Thu Jul 01 16:00:27 2010 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OUKJW-0007v4-Fe for ding-account@gmane.org; Thu, 01 Jul 2010 16:00:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1OUKIz-0005DM-A8; Thu, 01 Jul 2010 08:59:53 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1OUKIw-0005D2-5P for ding@lists.math.uh.edu; Thu, 01 Jul 2010 08:59:50 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1OUKIu-0007CU-At for ding@lists.math.uh.edu; Thu, 01 Jul 2010 08:59:49 -0500 Original-Received: from chirelay1o.jumptrading.com ([38.98.147.153] helo=chirelay1.jumptrading.com) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1OUKIt-0005LA-00 for ; Thu, 01 Jul 2010 15:59:47 +0200 Original-Received: from chirelay1.jumptrading.com (unknown [127.0.0.1]) by chirelay1.jumptrading.com (Symantec Mail Security) with ESMTP id 7A94A32000B for ; Thu, 1 Jul 2010 08:59:16 -0500 (CDT) X-AuditID: 26629395-a72f4bb000004d48-70-4c2c9f344fbf Original-Received: from chiexchange02.w2k.jumptrading.com (unknown [38.98.147.140]) by chirelay1.jumptrading.com (Symantec Mail Security) with ESMTP id 407762DC006 for ; Thu, 1 Jul 2010 08:59:16 -0500 (CDT) Original-Received: from internalsmtp.w2k.jumptrading.com (10.2.4.29) by chiexchange02.w2k.jumptrading.com (10.2.4.71) with Microsoft SMTP Server id 8.1.291.1; Thu, 1 Jul 2010 08:59:15 -0500 Original-Received: from tzlatanov-ubuntu-desktop.jumptrading.com ([10.2.14.81]) by internalsmtp.w2k.jumptrading.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Jul 2010 08:59:15 -0500 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" In-Reply-To: (Katsumi Yamaoka's message of "Thu, 01 Jul 2010 11:11:29 +0900") User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) X-OriginalArrivalTime: 01 Jul 2010 13:59:15.0758 (UTC) FILETIME=[9791A4E0:01CB1925] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:69775 Archived-At: On Thu, 01 Jul 2010 11:11:29 +0900 Katsumi Yamaoka wrote: KY> I use a sh script which does: KY> 1. Rearrange the files of Emacs into the directory structure that KY> is the same as Gnus. For instance, gather lisp/mail/binhex.el, KY> lisp/textmodes/dns-mode.el, etc. to lisp/; gather doc/misc/*.texi, KY> etc/refcards/gnus-refcard.tex, etc. to texi/, etc. OK. This is the part I plan to do semi-automatically with Bazaar-Git synchronization, which will track the files added or deleted on both sides. KY> 2. Apply the offset patch file to the gathered Emacs files. It KY> changes gnus-version-number, the default values of some user KY> options (mainly in message.el), etc. OK. Do you want me to look at your script and patch or write a whole new set? Do you want to keep synchronizing the two trees or would you rather make it a shared responsibility? I certainly don't mind if you do it. KY> 3. diff -aruN Gnus/ EmacsGnus/ KY> Normally it reports there's no difference. When it alerts, I check KY> if new comers work with Emacs 21~24, XEmacs 21.4/5, and SXEmacs 22.1. KY> And modify changes manually if needed, apply changes from one to KY> another manually, then commit them to Gnus, Emacs, or both. I have KY> no idea for a way to make those manual works automated. A buildbot setup can do it. I am discussing such a setup for the Emacs repo so it wouldn't be too much extra work to do it for Gnus as well. >> I'd like to help with the process (and automate it, as previously >> discussed) while adding these two features: >> - for a single change, make the commit message the same as the change's >> commit message (with a prefix to indicate it's a synch) KY> To make it worthwhile, we will need to improve commit messages so KY> as to say what they are for briefly in a single line. Easier said KY> than done, though. Anyway we should not use the ones such as the KY> following, that's just a copy of ChangeLog: KY> commit 08dd9f431367713667b1124e633c2ff97697a390 KY> Author: Katsumi Yamaoka KY> Date: Thu Jun 10 05:32:19 2010 +0000 KY> (gnus-mime-buttonized-part-id): New internal variable. KY> (gnus-article-edit-part): Bind it to make last part that is substituted KY> or deleted visible. KY> (gnus-mime-display-single): Buttonize part of which id equals to KY> gnus-mime-buttonized-part-id. I think the synchronizer (you or whoever does the process) should write the one-line abstract if the comitter doesn't. Let's keep the long format we already have for commit messages but put the one-line abstract on the very first line. So the above commit would be: "Buttonize part of the ID. (gnus-mime-buttonized-part-id): New internal variable. (gnus-article-edit-part): Bind it to make last part that is substituted or deleted visible. (gnus-mime-display-single): Buttonize part of which id equals to gnus-mime-buttonized-part-id." Then the Bazaar commit message can be just that first line. If there's no newline after the first line in our commit message, we'll know the comitter didn't provide a one-line summary. >> - close bugs when they are mentioned in the commit message >> I'd like this to be as automatic as possible, but never do a push >> automatically. So it can't happen on every commit. You didn't say yes or no; can I assume you're OK with this responsibility placed on the synchronizer? On Wed, 30 Jun 2010 22:34:55 -0400 Dave Goldberg wrote: >> BTW, is `No Gnus' really necessary? Though I've been maintaining >> it so as to work with various version of Emacsen, I don't know >> whether there are really a lot of people who use it. People who >> want the most recent Gnus can upgrade Emacs (if needed, even to >> use the Emacs head is not so troublesome). The only point may be >> that the Gnus XEmacs package is very old (it is now Gnus 5.10.8). DG> It is for this XEmacs user, for the exact reason you mention. Of DG> course I don't care whether you continue to call in No Gnus or turn it DG> into some other naming scheme if that makes it easier for the DG> maintainers. I do take advantage of several of the features, SMIME DG> related in particular, that are not available in the older versions. I think the current situation works for everyone. This is a question for Reiner, really, but I don't know if he's available and if he wants to continue doing Gnus releases and maintenance. Ted