**** BEGIN LOGGING AT Fri Apr 10 02:59:59 2015 Apr 10 07:27:48 good morning Apr 10 08:05:34 hi mckoan Apr 10 08:15:55 hi woglinde Apr 10 08:35:33 morning woglinde, mckoan, all Apr 10 08:39:06 hi bluelightning Apr 10 09:16:00 mornin Apr 10 11:00:35 Hello, given the gitorius shutdown some recipes I understand need to be updated. What is the corrrect procedure to report patches to fix those? Apr 10 11:01:57 oruizdorantes: it depends on the layer Apr 10 11:02:09 in general: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Apr 10 11:03:37 it is meta-oe but thanks for the link, it is what I was looking for Apr 10 11:05:04 meta-oe was not on gitorius Apr 10 11:05:10 a mirror perhaps Apr 10 11:08:03 woglinde: there is a recipe there which points to a gitorius repository can-utils for instance, maybe I am understanding the problem properly? let me know I am just getting involved Apr 10 11:08:07 woglinde: I think he means recipes that fetch from git repos on gitorious Apr 10 11:08:16 okay Apr 10 11:08:37 I thought jama will automagicly take care of them Apr 10 11:08:50 s/he/oruizdorantes/ that is Apr 10 11:09:28 woglinde: well, we ought not to assume JaMa will take care of everything, I'm sure he's busy enough ;) Apr 10 11:10:33 up to now had 2 crashes for this reason but the other belongs to a Freescale layer Apr 10 11:11:20 FWIW we are in the process of setting up a persistent source mirror to work around these kinds of issues Apr 10 11:12:02 to help in the time between the upstream going away and the recipe being fixed, that is Apr 10 11:13:10 bluelightning: thanks for feedback Apr 10 11:19:45 finally... the multi-kernel thing seems to work at last :) Apr 10 11:29:59 bluelightning: thanks :) Apr 10 15:33:50 hmm, the howto says patches should be in the body of the mail, but am I then allowed to write human text in there? basically I want to submit an idea for review, pretty sure it won't be taken as it is (although it works for me) Apr 10 15:34:00 and not sure what the best way would be to go about it Apr 10 15:34:24 Jin^eLD: Dunno about for OE but for the kernel it's common to just write a patch and tag it RFC. Apr 10 15:34:31 With discussion in the commit message. Apr 10 15:34:33 put RFC or similar in the subject line. describe it well in the body of the mail above the patch, etc Apr 10 15:34:36 * kergoth nods at broonie Apr 10 15:36:33 ok.. well its not a modification to the kernel itself, rather to kernel bbclasses, what's the "default" way to separate above body from the actual patch? Apr 10 15:36:58 just put it in the commit message part of the patch. Apr 10 15:37:40 just browse hte mailing lists, there are thousands of example patch emails to look at... Apr 10 15:39:55 kergoth: well I saw some after mail signature "--" and some other variations Apr 10 15:40:10 actually I was looking at the archives just about 5 minutes ago :) Apr 10 15:59:05 one more question Apr 10 16:00:02 I basically made changes in about 4 kernel relates bbclasses, they work only all together; should I nevertheless split them into several commits? or keep them as one? (those standalone commits would not be functional because it all has to come together) Apr 10 17:42:31 generally high granularity in commits is good, but having each commit be functional is more important or it breaks bisect Apr 10 17:42:48 so i'd say one in that particular case, unless you can break it up into multiple functioning pieces Apr 10 17:58:45 there are definiteluy reasons for non-functional group commits.. but there has to be a reason, vs just normal course of work Apr 10 17:59:00 (and it has to be clear that the bisect drops to the beginning of the series) Apr 11 00:51:02 Jin|away: all together if its not a huge patch together Apr 11 02:38:49 Hi I am trying to build custom kerenl for raspberrypi (3.18). I have set EXTERNALSRC_pn-linux-raspberrypi = <> in local.conf file located in build dir. I getting error when trying to compile kernel. Can someone help me to fix this issue ? Here is the error log: http://paste.ubuntu.com/10796839/ Apr 11 02:39:06 I am inherting externalsrc like this : INHERIT += "externalsrc" **** ENDING LOGGING AT Sat Apr 11 02:59:58 2015