All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: encourage switch away from heanet.sf.net
Date: Sun, 10 Dec 2006 22:30:37 +0000	[thread overview]
Message-ID: <1165789837.5604.41.camel@localhost.localdomain> (raw)
In-Reply-To: <ele3hp$u6v$1@sea.gmane.org>

On Sat, 2006-12-09 at 11:35 +0100, Rolf Leggewie wrote:
> Michael 'Mickey' Lauer wrote:
> >> Instead they automatically 302 you now.
> > 
> > If that's true, then +1 from me.
> 
> It seems they do.  And a sample session I wanted to provide as proof 
> apparently also revealed how they deal with the situation that a mirror 
> does not have the file.  I post only the relevant lines here.

I'm ok with trying this. I suggest checking with hrw and if he's ok with
it, apply it to .dev. Thanks for looking into it.

Cheers,

Richard




  reply	other threads:[~2006-12-10 22:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 13:15 RFC: encourage switch away from heanet.sf.net Rolf Leggewie
2006-12-08 13:19 ` Michael 'Mickey' Lauer
2006-12-09 10:35   ` Rolf Leggewie
2006-12-10 22:30     ` Richard Purdie [this message]
2006-12-11 20:44       ` Marcin Juszkiewicz
2006-12-12 12:14 ` Rolf Leggewie

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=1165789837.5604.41.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.