From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9727 invoked by alias); 4 Aug 2003 20:35:47 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 9720 invoked from network); 4 Aug 2003 20:35:46 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sources.redhat.com with SMTP; 4 Aug 2003 20:35:46 -0000 Received: from zaretski (pns03-199-55.inter.net.il [80.230.199.55]) by legolas.inter.net.il (Mirapoint Messaging Server MOS 3.3.5-GR) with ESMTP id AAU03263; Mon, 4 Aug 2003 23:35:33 +0300 (IDT) Date: Mon, 04 Aug 2003 20:35:00 -0000 From: "Eli Zaretskii" To: ac131313@redhat.com Message-Id: <2593-Mon04Aug2003233207+0300-eliz@elta.co.il> CC: gdb-patches@sources.redhat.com In-reply-to: <3F2EB6E8.3060100@redhat.com> (message from Andrew Cagney on Mon, 04 Aug 2003 15:41:28 -0400) Subject: Re: [patch,6.0,rfc,rfa:doco] Finish "mi2"/"mi3" rollover Reply-to: Eli Zaretskii References: <3F2EB6E8.3060100@redhat.com> X-SW-Source: 2003-08/txt/msg00046.txt.bz2 > Date: Mon, 04 Aug 2003 15:41:28 -0400 > From: Andrew Cagney > > This finishes the mi1/mi2/mi3 rollover. It also fixes a bug. The=20 > previous changes forgot to register "mi2", and set "mi" to "mi3".=20 > Anyway it: > > - adds "mi2" and "mi3" > - makes "mi" select "mi2" the last released "mi" version. > - updates the doco to mention that "mi2" was released in GDB 6.0 > - rolls the testsuite so that there is a frozen mi2-*.exp > > Note that "mi" is selecting "mi2" the last released version, and not the=20 > next version. This gives better consistency between the last branch and=20 > the current release - "mi" should select the same thing - and that might=20 > encourage people to pick up current snaps. > > I expect adding this to 6.0 and mainline in a few days. > > I should note that I'm not sure how consistent my rollover process is -=20 > I suspect last time "mi" ended up selecting the mainline, instead of the=20 > previous released version. I guess, given miN as the default, the=20 > process is: > > Freeze an MI version (on the branch): > - delete mi{N-1} > - make "mi" select mi{N+1} > - copy mi{N+1}-*.exp to mi-*.exp, s/-i=3Dmi{N+1}/-i=3Dmi/ > > Start a new MI version (on the mainline): > - add mi{N+2} > - copy mi{N+1)-*.exp to mi{N+2}-*.exp, s/-i=3Dmi{N+1}/-i=3Dmi{N+2}/ > > thoughts? The docs part is okay with me.