From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ralf Angeli Newsgroups: gmane.emacs.devel,gmane.emacs.auctex.devel Subject: Re: Ways of keeping Emacs 22 and external projects in sync Date: Mon, 01 Jan 2007 16:21:18 +0100 Message-ID: References: <87k60b7hv5.fsf@neutrino.caeruleus.net> <85irftmi8p.fsf@lola.goethe.zz> <87k60b7hv5.fsf@neutrino.caeruleus.net> <87sley46bb.fsf@neutrino.caeruleus.net> <87mz554e1u.fsf@neutrino.caeruleus.net> <20061231222721.GA1424@kobe.laptop> <87fyav1uwb.fsf@neutrino.caeruleus.net> <87slev5ilm.fsf_-_@hariken.mwolson.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1167664925 19406 80.91.229.12 (1 Jan 2007 15:22:05 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 1 Jan 2007 15:22:05 +0000 (UTC) Cc: auctex-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 01 16:22:04 2007 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 1H1OzB-0003Al-VQ for ged-emacs-devel@m.gmane.org; Mon, 01 Jan 2007 16:22:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1OzB-0008NY-3D for ged-emacs-devel@m.gmane.org; Mon, 01 Jan 2007 10:22:01 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1Oyx-0008N4-Sm for emacs-devel@gnu.org; Mon, 01 Jan 2007 10:21:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1Oyx-0008MZ-4X for emacs-devel@gnu.org; Mon, 01 Jan 2007 10:21:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1Oyw-0008MW-Sk for emacs-devel@gnu.org; Mon, 01 Jan 2007 10:21:47 -0500 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H1Oyw-0001NW-C8 for emacs-devel@gnu.org; Mon, 01 Jan 2007 10:21:46 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H1Oyn-0006kT-RG for emacs-devel@gnu.org; Mon, 01 Jan 2007 16:21:37 +0100 Original-Received: from p54a528b4.dip0.t-ipconnect.de ([84.165.40.180]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Jan 2007 16:21:37 +0100 Original-Received: from angeli by p54a528b4.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Jan 2007 16:21:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 108 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p54a528b4.dip0.t-ipconnect.de User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux) Cancel-Lock: sha1:Mfi0jwhOfOPE9O+a1LD0mYFO6kQ= 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:64601 gmane.emacs.auctex.devel:1493 Archived-At: * Michael Olson (2007-01-01) writes: > I guess I'll chip in with how I manage to keep the development version > of ERC synced with that included with Emacs 22. Gnus does it slightly > different than I do, because they merge directly to Emacs 22, rather > than using an intermediary branch like I do. AFAIK changes to Gnus files in Emacs' repository will be transferred automatically via Miles' Arch repositories to Gnus' stable branch. I'm not sure how changes relevant to the trunk are moved there. > I use GNU Arch to maintain ERC. Among the various branches are these: > > erc--main--0 :: Where development happens > > erc--rel--5.1 :: Where the currently previous major release (5.1) gets > updated when it is time to prepare a minor release. > > erc--emacs--22 :: The branch which is used to sync to and from the > version in Emacs 22. > > emacs--devo--0 :: The equivalent of CVS HEAD for Emacs in Arch, kept > in sync by Miles Bader. [...] > I then set up a couple of scripts (in a scripts/ directory that only > exists in the erc--emacs--22 branch) that help me sync to and from the > Emacs 22 source tree. [...] > sync-from-emacs: > === > #!/bin/bash > > # Load common definitions > . scripts/common.defs > > (cd $LISP/erc && find . -maxdepth 1 -mindepth 1 -type f -exec cp {} $OLDPWD \;) > cp $ETC/ERC-NEWS etc/ > cp $MAN/erc.texi man/ > rm -f *.elc > === > > sync-to-emacs: > === > #!/bin/bash > > # Load common definitions > . scripts/common.defs > > (cd $LISP/erc && find . -maxdepth 1 -mindepth 1 -type f -exec cp {} $OLDPWD \;) > cp $ETC/ERC-NEWS etc/ > cp $MAN/erc.texi man/ > rm -f *.elc > === The scripts look identical. Is that correct? > * Syncing changes > > When there are some changes that need to be propagated to Emacs 22, I So you are updating ERC in Emacs not on a release-by-release basis, but rather when some important changes need to be propagated? Do you apply a tag in that case in order to identify the file revisions if somebody has a bug report or support request referring to the ERC version in Emacs or do you just use the files in Emacs directly for testing and debugging? > first check emacs--devo--0 to see if someone changed things on the > Emacs side, by running ./scripts/sync-from-emacs. If anything is > different than the current contents of erc--emacs--22, I immediately > check them in (to erc--emacs--22). Do you regularly synch from Emacs or just when you are about to synch to Emacs? My idea for RefTeX would have been that a synch from Emacs to RefTeX is done regulary, but directly instead of using an intermediate repository. > I also think it is a very bad idea for Emacs developers to mandate > checking in files individually. It might make sense for work on the > core files in lisp/emacs-lisp/ or the top-level of lisp/, but a > significant percentage of changes made to the other lisp files involve > changing several files at once. Separating log entries for commit > messages begins to become a burden. For operations such as updating > an entire project, this would become very tedious (not to mention > unnecessary, because ChangeLog contains all the information that is > really needed). That reminds me: When you are synching from Emacs to ERC (and vice versa) the ChangeLog file is probably handled the same way Lisp files are. Because log entries of changes to RefTeX in Emacs currently end up in lisp/ChangeLog we'd need a separate ChangeLog file for RefTeX for this to work. > With Arch, such changes are treated as a single change to the entire > project, rather than multiple separate changes to single files. There > is no possibility (however remote) of changes to several files being > only partially applied, as long as Arch is the only version control > system involved. As Savannah supports Arch repositories now it should be no problem to maintain RefTeX in such a repository. What I would be missing with Arch would be something like PCL-CVS and the web interface like Savannah provides it for CVS repositories. -- Ralf