On Tue, Mar 31, 2015 at 9:17 AM, Paul Eggleton <paul.eggle...@linux.intel.com> wrote: > Hi Chris, > > Great to see you at ELC! > > On Monday 30 March 2015 19:17:46 Chris Hallinan wrote: >> Great catching up with you last week, and thanks for looking at my >> patch. I supposed it's a double edged sword. If we make it a >> variable, it can be set wrong and the build hang again. OTOH, 128MB >> is probably way more space than we really need to reserve, and I >> supposed if someone were just banging up against the limit, they might >> want to tweak it. I'll defer to the collective judgement of the >> group, and resubmit if that's the consensus. > > Is there any practical way we can measure the actual size of these files?
I gave this some thought after Armin's comment, and yes, maybe there is a way to estimate the size available. I'll look further into it. > >> Oh, and silly me...I figured the mail list daemon would put the >> [Yocto] tag on the patch. Since it seems to tag our posts, that is a >> mystery to me. > > The mailing list always prepends the list name to the subject of posted > messages. That what I thought, too. Wonder why it didn't prepend the list name to this patch? > A few other notes: > > 1) This patch should be sent to the openembedded-c...@lists.openembedded.org > mailing list rather than here. Ah, wasn't sure about that, thanks! > > 2) The YP bugzilla reference should be of the format [YOCTO #7541] . > > 3) The shortlog (first line of the commit message / subject) should be > prefixed > with the area/file the patch is changing i.e. for this one it should be > "bootimg.bbclass: gracefully abort if rootfs.img gets to big". Thanks for the guidance. As you can see, I'm not experienced at sending patches! I'll investigate and re-send to oe-core@ Regards, Chris -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto