From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Francis Moreau Newsgroups: gmane.emacs.help Subject: Re: What's the status of the emacs' git repo on savannah Date: Sun, 7 Jun 2009 09:08:47 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <87vdnb6s9x.fsf@lion.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1244392864 15215 80.91.229.12 (7 Jun 2009 16:41:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 7 Jun 2009 16:41:04 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jun 07 18:41:01 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MDLQY-0002OR-QR for geh-help-gnu-emacs@m.gmane.org; Sun, 07 Jun 2009 18:40:59 +0200 Original-Received: from localhost ([127.0.0.1]:36054 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MDLQY-0001GO-AF for geh-help-gnu-emacs@m.gmane.org; Sun, 07 Jun 2009 12:40:58 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!x3g2000yqa.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 56 Original-NNTP-Posting-Host: 82.235.205.153 Original-X-Trace: posting.google.com 1244390927 7845 127.0.0.1 (7 Jun 2009 16:08:47 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sun, 7 Jun 2009 16:08:47 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: x3g2000yqa.googlegroups.com; posting-host=82.235.205.153; posting-account=ekTE0goAAADiVCThPmo4ph0C5bTUhQOx User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.10) Gecko/2009042708 Fedora/3.0.10-1.fc10 Firefox/3.0.10, gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:169782 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:65015 Archived-At: On 5 juin, 09:42, Tim X wrote: > Francis Moreau writes: > > On Jun 3, 11:50=A0pm, Thierry Volpiatto > > wrote: > >> Francis Moreau writes: > >> > Hello, > > >> > I'm wondering if this repo is kept uptodate frequently. > > >> > I cloned, compiled and installed emacs from the master branch which > >> > points to this commit: 8e282b1c43fd6768a9ec339f5cb8aefd4d2fc2 > >> > Date: =A0 Wed Apr 29 04:46:15 2009 +0000 > > >> > Asking to the freshly installed emacs its version gives me: > > >> > $ emacs --version > >> > GNU Emacs 23.0.92.1 > > >> > I don't think it is the latest emacs. > > >> > Does anybody have any information on this repo ? > > >> I think emacs developpers are working actually on the savannah repo. > >> It's better waiting all problems are fixed before (re)installing emacs= . > > > Can't I use this repo to retrieve pre-release or something like ? > > > In the repo, there are tags such as: EMACS_PRETEST_23_0_92. > > > Is it 'safe' to use such revisions ? > > > Also I saw that some people are using emacs 23.0.94. Where do they get > > this release if it's not in the dev repo ? > > > thanks > > Just to clarify > > The savannah server had a hardware fault (disk I think) a few days > back. Unfortunately, due to issues with their backups, they didn't/don't > have a recent backup of many of the source code repositories. Therefore, > they are having to get versions pushed back from developer's own git > repositories (not sure what they plan for the cvs and svn repos). > > What this means is that the current repository is likely the one from > the last reliable backup, which I think may have been as far back as > April. > > So, my advice would be to wait another few days and see if the > repository becomes more up-to-date. > thanks for clarifying, actually the server seemed to become up to date once Giorgos replied.