From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] udev-extraconf: update mount.sh to use /run/media instead of /media
Date: Mon, 07 Apr 2014 23:22:11 +0100 [thread overview]
Message-ID: <1396909331.24597.84.camel@ted> (raw)
In-Reply-To: <20140407210549.GI3370@denix.org>
On Mon, 2014-04-07 at 17:05 -0400, Denys Dmytriyenko wrote:
> I understand the timing concern and am fine waiting another week for when 1.7
> window opens.
>
> But I'm slightly confused as to since when OE-Core is concerned about breaking
> bbappends in other layers? I guess some layers are not created equal, eh? :)
The question is more one of timing. I don't think its reasonable that we
break things like that between -rc2 and -rc3 of 1.6 without a better
reason...
I'm even nervous changing the sstate checksums but I think the CONFFILES
change does warrant that for example.
Cheers,
Richard
next prev parent reply other threads:[~2014-04-07 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 3:54 [PATCH v2] udev-extraconf: update mount.sh to use /run/media instead of /media Denys Dmytriyenko
2014-04-06 22:46 ` Denys Dmytriyenko
2014-04-07 15:49 ` Saul Wold
2014-04-07 21:05 ` Denys Dmytriyenko
2014-04-07 22:22 ` Richard Purdie [this message]
2014-04-21 17:26 ` Denys Dmytriyenko
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=1396909331.24597.84.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=denis@denix.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox