public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Iqbal <iqbal@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: source.mvista links are broken
Date: Fri, 4 Apr 2008 14:03:15 +0300	[thread overview]
Message-ID: <20080404110314.GN3505@atomide.com> (raw)
In-Reply-To: <5D8B5EC1EB6ED845B1EB216F00C71B65032A8F0F@dlee12.ent.ti.com>

* Iqbal <iqbal@ti.com> [080404 13:07]:
> 
> Looks like the OMAP tree links are broken and the summary,short log and other fields don't work.
> 
> http://source.mvista.com/git/?p=linux-omap-2.6.git;a=commit;h=8a88c221c88399bc694c367dbea01ffc4153ef20

Yeah, I've noticed that too. Probably git needs updating on
source.mvista.com, it seems to have issues with reading packed objects.

I've fixed it to some extent by scp'ing over some object files, and then
there was a brief file permissions problem too...

In any case, please use the kernel.org instead:

http://git.kernel.org/git/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git

I've notified Kevin about the issue, so we probably have to wait for
git to get updated.

Tony

  reply	other threads:[~2008-04-04 11:03 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 [this message]
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
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=20080404110314.GN3505@atomide.com \
    --to=tony@atomide.com \
    --cc=iqbal@ti.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