public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@alum.bu.edu>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: overseers@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: savannah trailing sources?
Date: Sun, 09 May 2004 18:46:00 -0000	[thread overview]
Message-ID: <20040509160728.GA17005@coe.bosbc.com> (raw)
In-Reply-To: <20040509152220.GA4103@redhat.com>

On Sun, May 09, 2004 at 11:22:20AM -0400, Aldy Hernandez wrote:
>[Ok, one more time with the right address.  Doh!]
>
>Hi folks.
>
>Is savannah supposed to trail sources on purpose?
>
>Savannah:
>
>   coqui:/tmp/x/gcc/gcc$ cvs status ChangeLog
>   ===================================================================
>   File: ChangeLog         Status: Up-to-date
>    
>      Working revision:    2.3607
>      Repository revision: 2.3607  /cvsroot/gcc/gcc/gcc/ChangeLog,v
>
>Sources:
>
>   coqui:/source/uber/gcc$ cvs status ChangeLog
>   ===================================================================
>   File: ChangeLog         Status: Up-to-date
>    
>      Working revision:    2.3611
>      Repository revision: 2.3611  /cvs/uberbaum/gcc/ChangeLog,v
>
>Cheers.

When system b mirrors system a by taking periodic snapshots it is pretty
much a guarantee that system b will trail system a.

This really isn't an overseers issue.  We don't control Savannah.

cgf

  reply	other threads:[~2004-05-09 17:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09 15:24 Aldy Hernandez
2004-05-09 18:46 ` Christopher Faylor [this message]
2004-05-09 17:26   ` Aldy Hernandez
2004-05-09 23:27     ` Christopher Faylor
2004-05-09 20:46   ` Andreas Schwab
2004-05-10  2:17     ` Christopher Faylor
2004-05-10  2:36       ` Jeff Sturm
2004-05-10  2:44         ` Christopher Faylor
2004-05-10  2:50           ` Matthew Galgoci
2004-05-10  2:55             ` Andreas Jaeger
2004-05-10  2:55               ` Matthew Galgoci
2004-05-10 13:59                 ` Phil Edwards
2004-05-10  4:54             ` Zack Weinberg
2004-05-10 14:00         ` Dave Korn
2004-05-10 14:01       ` Andreas Jaeger
2004-05-10 14:10       ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040509160728.GA17005@coe.bosbc.com \
    --to=cgf@alum.bu.edu \
    --cc=aldyh@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=overseers@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).