public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: "'ecos-discuss@sourceware.org'" <ecos-discuss@sourceware.org>,
	 Jonathan Larmour <jifl@eCosCentric.com>
Cc: eCos discussion <ecos-discuss@sources.redhat.com>,
	eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: RE: [ECOS] sources.redhat.com downtime
Date: Fri, 17 Jan 2003 20:34:00 -0000	[thread overview]
Message-ID: <9F77D654ED40B74CA79E5A60B97A087B0423CE@sd-exchange.sdesigns.com> (raw)

Are they going to upgrade the cvs server to a new version of cvs also?

I remember the current one has an annoying bug when making diff (If i
remember correctly...)

-- 
Fabrice Gautier, 
Fabrice_Gautier@sdesigns.com


> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> Sent: Thursday, January 16, 2003 10:32 PM
> To: Jonathan Larmour
> Cc: eCos discussion; eCos Maintainers
> Subject: Re: [ECOS] sources.redhat.com downtime
> 
> 
> On Thu, Jan 16, 2003 at 10:57:06PM +0000, Jonathan Larmour wrote:
> >It's not much warning,
> 
> I would have given more, if I could.
> 
> >but it's just been revealed that the long promised upgrade of
> >sources.redhat.com will take place this coming Saturday at:
> >
> >10am PST
> > 1pm EST
> > 6pm GMT
> > 7pm CET
> >
> >and no doubt other timezones :-).
> >
> >It will probably not return until Sunday morning. At a 
> minimum it will be 
> >three hours if everything goes well, but don't count on it. 
> If it's not 
> >up, it's not up.
> >
> >All services will be off-line at that point: no cvs, web, 
> ftp, or mailing 
> >lists. We can't even hear you scream ;-).
> >
> >It's definitely worth it as it will be a move to a much 
> newer, faster and 
> >larger machine.
> 
> And one with a lot more net bandwidth, too.  It's better in every way.
> 
> Now, if *that* doesn't jinx me, nothing will.
> 
> >That should make for a quiet weekend :).
> 
> For some people, maybe.  :-)
> 
> cgf
> 
> -- 
> Before posting, please read the FAQ: 
http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2003-01-17 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 20:34 Fabrice Gautier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-16 22:57 Jonathan Larmour
2003-01-17  6:31 ` [ECOS] " Christopher Faylor

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=9F77D654ED40B74CA79E5A60B97A087B0423CE@sd-exchange.sdesigns.com \
    --to=fabrice_gautier@sdesigns.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=ecos-discuss@sourceware.org \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jifl@eCosCentric.com \
    /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).