From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: Kevin Hilman <khilman@mvista.com>, linux-omap@vger.kernel.org
Subject: Re: source.mvista links are broken
Date: Tue, 8 Apr 2008 20:08:40 +0000 [thread overview]
Message-ID: <20080408200839.GA31071@atomide.com> (raw)
In-Reply-To: <010C7BAE6783F34D9AC336EE5A01A08805C30581@dbde01.ent.ti.com>
* Gadiyar, Anand <gadiyar@ti.com> [080408 08:30]:
> <snip>
>
> >
> > I'm still unable to clone the git tree from the mvista site.
> >
> > I use "git clone http://source.mvista.com/gittrees/linux-omap-2.6.git"
> >
> > I can't use the git://* URLs either. I'm behind a proxy and exporting
> > http_proxy isn't helping.
> >
>
> Was finally able to clone from kernel.org. Found the correct http URL from
> http://www.muru.com/linux/omap/README_OMAP_GIT.
>
>
> > At least, I'm able to browse the tree from the mvista server and get
> > file changelogs, etc from there.
>
Sorry for the delay on this, I did not get a chance to look into this
during the weekend, and then was travelling back home on Monday.
Well I ran git-fsck --full on source.mvista.com, and it produced missing
links errors.
So I just cloned the repo from kernel.org and added back the branches.
It should work now, let me know if any issues.
I have no idea what might have corrupted the repo, maybe disk errors?
Regards,
Tony
next prev parent reply other threads:[~2008-04-08 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 10:06 source.mvista links are broken Iqbal
2008-04-04 11:03 ` Tony Lindgren
2008-04-04 18:16 ` Kevin Hilman
2008-04-06 14:44 ` Dirk Behme
2008-04-08 4:37 ` Gadiyar, Anand
2008-04-08 8:30 ` Gadiyar, Anand
2008-04-08 20:08 ` Tony Lindgren [this message]
2008-04-09 7:08 ` Trilok Soni
2008-04-09 11:53 ` Woodruff, Richard
2008-04-09 23:23 ` Kyungmin Park
2008-04-09 23:40 ` Woodruff, Richard
2008-04-10 2:59 ` Kevin Hilman
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=20080408200839.GA31071@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=khilman@mvista.com \
--cc=linux-omap@vger.kernel.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