All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: invalid git commit for beagle in u-boot recipe?
Date: Sun, 29 Nov 2009 06:33:59 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911290633120.8046@localhost> (raw)
In-Reply-To: <20091128221627.GA29288@denix.org>

On Sat, 28 Nov 2009, Denys Dmytriyenko wrote:

> On Sat, Nov 28, 2009 at 02:46:52PM -0500, Robert P. J. Day wrote:
> >
> >   as best i can tell, this entry in u-boot_git.bb on the OE dev
> > branch:
> >
> > SRCREV_beagleboard = "1590f84007e2b50ad346a482fff89195cb04ff4e"
> >
> > refers to an invalid commit.  this is what happens when i build for
> > the beagle:
> >
> > NOTE: preferred version git of u-boot not available (for item u-boot)
> >
> > just an observation.
>
> The message above has nothing to do with the commit number
> specified. The problem is with PV being overwritten for beagleboard
> to specify a proper version, while PREFERRED_VERSION still wants
> "git"...

  ok, but isn't it still an issue that that commit appears to exist
nowhere in that git repo?  i scanned the log and that commit tag
simply doesn't show up.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



  reply	other threads:[~2009-11-29 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28 19:46 invalid git commit for beagle in u-boot recipe? Robert P. J. Day
2009-11-28 22:16 ` Denys Dmytriyenko
2009-11-29 11:33   ` Robert P. J. Day [this message]
2009-12-09 21:48     ` Cliff Brake

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=alpine.LFD.2.00.0911290633120.8046@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-devel@lists.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.