**** BEGIN LOGGING AT Mon Jan 25 02:59:57 2021
Jan 25 08:46:41 <hrw> Crofton|cloud: thanks for link
Jan 25 15:29:28 <fray> I need a clue, I've got a recipe that depends on gstreamer1.0-plugins-base, which itself has a bbappend that changes based on some configurations.  But I've determined that my recipe doesn't matter what the config is, as long as it exists.  I'm trying to understand if I should be using SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS or SIGGEN_EXCLUDE_RECIPES_ABISAFE, when the config changes in gstreamer, it causes my recipe to rebuild and I don't want that
Jan 25 15:32:20 <fray> I'm guessing it's the former, but I'm not sure
Jan 25 15:53:44 <clementp[m]> Hi, is the patchwork tool down ? https://patchwork.openembedded.org/project/oe/patches/?archive=both&state=*
Jan 25 15:53:50 <clementp[m]> seems latest patches aren't listend
Jan 25 17:11:05 <weather> Hi, I want to share a patch for pseudo and don't know how to do so. Which mailing list should I use? And is it normal to send first a patch for pseudo and let it go naturally into openembedded via a recipe update, or instead a send patch for the recipe and let it go upstream into pseudo by someone else? Thanks
Jan 25 17:41:54 <armpit> weather, openembedded-core@lists.openembedded.org
Jan 25 17:42:06 <weather> thanks!
Jan 25 17:53:30 <paulbarker> Crofton|cloud: I set up a couple of repos for the stand website content and emailed the stands mailbox, no reply yet
Jan 25 17:53:55 <Crofton|cloud> I'll try and clone them
Jan 25 17:54:04 <paulbarker> Crofton|cloud: Looks like they added it and never replied to me: https://github.com/FOSDEM/stands-website/tree/master/content/stands
Jan 25 17:54:29 <paulbarker> See https://gitlab.com/openembedded/community for our content + static files
Jan 25 17:54:30 <Crofton|cloud> can we update?
Jan 25 17:55:29 <paulbarker> I hope that their top-level stands repo follows new commits to the individual content & static files repos
Jan 25 17:55:36 <paulbarker> I asked that in the email but no reply as I say
Jan 25 17:55:43 <paulbarker> They're probably swamped
Jan 25 17:55:47 <paulbarker> And I am as well
Jan 25 17:55:58 <paulbarker> I'll take another look at it briefly this weekend but that's it
Jan 25 17:56:12 <paulbarker> In my email to the list I asked for someone else to step up and take the lead on this
Jan 25 17:56:28 <paulbarker> If that doesn't happen I'll throw together a paragraph or two of text and call it good enough
Jan 25 18:10:29 <Crofton|cloud> Having a place holder helps
Jan 25 18:11:02 <Crofton|cloud> clearly they should be using submodules :)
Jan 25 18:13:58 <halstead> clementp[m], Yes patch processing has been routinely timing out. I can try re-processing missed email.
Jan 25 18:15:42 <smurray> Crofton|cloud: actually, the more typical approach would be if they wrote their own tool to nest the repositories
Jan 25 18:16:05 <Crofton|cloud> heh
Jan 25 18:17:42 <clementp[m]> halstead: thanks :) 
Jan 25 18:18:38 <Crofton|cloud> So any downside to enabling the ptest distro feature? Besides having the extra packages built?
Jan 25 18:27:33 <paulbarker> Crofton|cloud: They are using submodules
Jan 25 18:27:55 <Crofton|cloud> ah good :)
Jan 25 18:28:05 <Crofton|cloud> I was just making wild speculation
Jan 25 18:28:08 <paulbarker> My wonder is whether they update the submodule revisions automatically or if I need to send them another email or pull request every time we push to our repos
Jan 25 18:28:40 <Crofton|cloud> I'll keep my eyes open
Jan 25 18:29:04 <paulbarker> Cheers
**** ENDING LOGGING AT Tue Jan 26 02:59:57 2021