All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: New parse error in dev
Date: Sun, 15 Nov 2009 22:09:56 +0100	[thread overview]
Message-ID: <20091115210956.GB3317@jama> (raw)
In-Reply-To: <4B00654D.3010507@balister.org>

On Sun, Nov 15, 2009 at 03:32:13PM -0500, Philip Balister wrote:
> Commit:
> 
> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=f18414059f60ec5924a702a227069aac09f19a0b
> 
> I don't see a quick fix, can someone knowledgeable about shr please
> fix this ASAP.
> 
> Philip

Sorry for that.. fixed with 29d6bcd8585aff0833eb88c06c3cc2474675c25c

Just removed that inherit, libmodulo was only user of girepository class
so we'll add it to libmodulo recipe directly if still needed (need to
ask mickey before..)

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



      parent reply	other threads:[~2009-11-15 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 20:32 New parse error in dev Philip Balister
2009-11-15 21:08 ` Leon Woestenberg
2009-11-15 21:09 ` Martin Jansa [this message]

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=20091115210956.GB3317@jama \
    --to=martin.jansa@gmail.com \
    --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.