All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Multiple .bb files are due to be built which each provide udev
Date: Sun, 23 Dec 2012 22:21:45 +0100	[thread overview]
Message-ID: <20121223222145.6785dca1@eb-e6520> (raw)
In-Reply-To: <B7FA4357-A7A1-408A-AF1F-89062AAACF8D@dominion.thruhere.net>

Le Sun, 23 Dec 2012 20:36:29 +0100,
Koen Kooi <koen@dominion.thruhere.net> a écrit :
> > I'll revert the patch tomorrow (monday)
> 
> So how are you going to fix the upgrade paths? Version downgrades are a serious regression as well.

upgrade path is not a problem here as builds are borken if we don't
change a setting in the conf files so I'll revert it so that users
don't need to change anything to their settings (and that won't
even break angstrom as the fix is not yet pushed as you stated in your
answer).

Eric



  reply	other threads:[~2012-12-23 21:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMBWrQnMQtEs78=OtkSR1mjctfet8ArQ_XE43wDB6-6NKiDShA@mail.gmail.com>
2012-12-21 20:58 ` Multiple .bb files are due to be built which each provide udev Stan Hu
2012-12-21 21:11   ` Martin Jansa
2012-12-21 21:18     ` Stan Hu
2012-12-22  9:03       ` Eric Bénard
2012-12-22 10:10         ` Koen Kooi
2012-12-22 11:05           ` Eric Bénard
2012-12-23 14:47             ` Eric Bénard
2012-12-23 18:10               ` Koen Kooi
2012-12-23 18:15                 ` Eric Bénard
2012-12-23 18:53                 ` Eric Bénard
2012-12-23 19:36                   ` Koen Kooi
2012-12-23 21:21                     ` Eric Bénard [this message]
2012-12-23 22:16                       ` Koen Kooi
2012-12-24  8:06                         ` Eric Bénard
2012-12-24  8:39                           ` Koen Kooi

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=20121223222145.6785dca1@eb-e6520 \
    --to=eric@eukrea.com \
    --cc=koen@dominion.thruhere.net \
    --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.