All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Allen, Scott (ITS)" <sallen@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>,
	Jon Szymaniak <jon.szymaniak+gpg@gmail.com>
Subject: Re: linux-ti-staging fetcher failures
Date: Thu, 2 May 2013 15:28:02 -0400	[thread overview]
Message-ID: <20130502192802.GC2364@edge> (raw)
In-Reply-To: <31331E6D91818F49B78B9920E96E64C704A3B444@DFLE08.ent.ti.com>

Thanks, Scott!

On Thu, May 02, 2013 at 02:45:09PM -0400, Allen, Scott (ITS) wrote:
> All, network team has identified a routing issue and made some corrections. 
> Initial testing indicates this resolved the problem.
> 
> Please try/ test again and let me know if the problem continues.
> 
> -scott
> 
> 
> -----Original Message-----
> From: jon.szymaniak@gmail.com [mailto:jon.szymaniak@gmail.com] On Behalf Of Jon Szymaniak
> Sent: Sunday, April 28, 2013 9:10 PM
> To: Dmytriyenko, Denys
> Cc: Allen, Scott (ITS); meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] linux-ti-staging fetcher failures
> 
> On Sun, Apr 28, 2013 at 4:10 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> > On Sun, Apr 28, 2013 at 01:50:55PM -0400, Jon Szymaniak wrote:
> >> Hi all,
> >>
> >> I just wanted to inquire about the status of git.ti.com, which the 
> >> linux-ti-staging_3.8.bb recipe clones from.
> >>
> >> I've been trying to bring up my am335xevm, and have been constantly 
> >> getting timeouts from git.ti.com for the last few days.  I've had no 
> >> luck manually cloning the kernel from this server -- is this not publicly accessible?
> >
> > Jon,
> >
> > Thanks for your inquiry! Unfortunately, I also noticed that git.ti.com 
> > was not accessible from outside since at least Friday. I will let our 
> > admins know, so they can take a look at the problem. Sorry for the inconvenience.
> >
> > --
> > Denys
> 
> Thank you Denys!
> 
> FWIW, a friend of mine who's a couple miles away and on the same ISP is able to clone the kernel and visit the git web front-end.  Nothing jumped out at me when comparing our traceroute/tracepath results -- everything's largely the same. I also see that ICMP seems blocked for me, but not for him.
> 
> Strange...let me know if I can provide any useful info.
> 
> - Jon


  reply	other threads:[~2013-05-02 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 17:50 linux-ti-staging fetcher failures Jon Szymaniak
2013-04-28 20:10 ` Denys Dmytriyenko
2013-04-29  2:09   ` Jon Szymaniak
2013-05-02 18:45     ` Allen, Scott (ITS)
2013-05-02 19:28       ` Denys Dmytriyenko [this message]
2013-05-04 19:36         ` Jon Szymaniak

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=20130502192802.GC2364@edge \
    --to=denys@ti.com \
    --cc=jon.szymaniak+gpg@gmail.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=sallen@ti.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 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.