| Saturday, February 25th, 2012, 00:03 UTC | ||
| [00:03:14] | Beirdo (Beirdo!~gjhurlbu@mythtv/developer/beirdo) has joined #mythtv-theming | |
| [00:03:31] | ** Beirdo pats the bot. Good boy. ** | |
| [00:04:03] | sphery: | Captain_Murdoch: I was thinking about moving Mythbuntu and Childish themes out of https://github.com/MythTV/myththemes and into https://github.com/MythTV-Themes before 0.25 is released, then we can just "delete" the myththemes repo, which will encourage users not to install myththemes and use the Theme Chooser, instead (and get all the updates and such). Might also make it less likely for packagers to package themes (I hope). |
| [00:04:12] | sphery: | My current plan is to use git filter-branch to split the myththemes repo out into 2 completely separate repos, one for Mythbuntu and one for Childish (containing only the information on that specific theme--throwing out info on all the other themes that used to be in there). Those repos would be hosted as separate repos on https://github.com/MythTV-Themes , and we'd be able to set up permissions on a repo-by-repo basis. |
| [00:04:17] | sphery: | Sound like a good plan to you? Should I go for it and then push the new repos? |
| [00:07:00] | Captain_Murdoch: | sounds good to me. |
| [00:07:27] | Captain_Murdoch: | jpabq, your theme is up now. I forgot to update the index the other night, but just refreshed it and verified it's available for download. |
| [00:07:32] | sphery: | Excellent! (/me drums his fingers together) |
| [00:27:33] | jpabq: | Captain_Murdoch, cool. Thanks. |
| [01:04:36] | sphery: | Captain_Murdoch: last question... I noticed lynchmv just put Childish in his repo--without configure and cpsimple and ... Is that the approach we want? So then a maintainer/author could just clone into ~/.mythtv/themes and work right there (and not have to worry about configure/make/make install)? |
| [01:06:50] | sphery: | his was https://github.com/lynchmv/Childish (though I think he wants to "retire" that one and keep the one that's currently in myththemes) |
| [01:47:10] | Captain_Murdoch: | no need for a theme to have a configure unless the themer wants to go out of his way to provide one. not much need with the theme downloader though. |
| [01:50:15] | Captain_Murdoch: | are you going to make a subdir below the repo? MythTV-Themes/Childish/Childish/themeinfo.xml or MythTV-Themes/Childish/themeinfo.xml |
| [01:51:53] | Beirdo: | current thought it right at the top dir, will that be an issue? |
| [01:53:00] | Captain_Murdoch: | no, my script works with either. only reason I can think of to make a subdir is to have 4:3 and 16:9 versions of a theme in the same repo. |
| [01:53:06] | Beirdo: | ahh |
| [01:54:39] | Captain_Murdoch: | and I still think I'd like to have the concept of a 'fallback theme' that we fall back to before default. so, in one repo, you might have a main theme and several sub-themes with perhaps different color themes. |
| [01:55:10] | Captain_Murdoch: | implementation is just a small bit of codeto insert a new directory into the search path. |
| [01:55:48] | Captain_Murdoch: | then it's up to the theme downloader to install the prerequesite theme if you don't have it already. |
| [02:01:58] | Beirdo: | ahh, nice |
| [02:03:44] | Captain_Murdoch: | I was playing with a patch before freeze but didn't have time to get it done so I backed it out of my tree until later. |
| [02:07:35] | Beirdo: | branches are useful for that :) |
| [02:08:42] | Captain_Murdoch: | yeah, but if I do have enough time to code, I'd rather spend it on a bugfix. |
| [02:09:01] | Beirdo: | definitely |
| [02:09:31] | Beirdo: | I meant... just stash it on a branch, come back to it later :) but definitely we wanna bugfix at this point |
| [02:14:14] | sphery: | Captain_Murdoch: also, about Mythbuntu theme, Beirdo noticed that it has a couple of commits on https://github.com/gbutters/myththemes/commits/master/ that don't seem to be in https://github.com/MythTV/myththemes/commits/master/Mythbuntu . Should I email gbutters to ask him whether he wants us to move ours to MythTV-Themes or keep using his or move his to MythTV-Themes? |
| [02:16:02] | Captain_Murdoch: | yeah, I'd ask. if he's maintaining it elsewhere,I can pull from his repo when to package. |
| [02:16:42] | Captain_Murdoch: | s/ to/ I/ don't know where that came from. |
| [02:17:05] | sphery: | yeah, not sure which one is good... too many repos/copies :) |
| [02:17:20] | sphery: | I'm pretty sure we have stuff on our copy that's not on his, too |
| [02:17:29] | Beirdo: | we do |
| [02:17:32] | Captain_Murdoch: | yep |
| [02:17:36] | sphery: | So, I think Beirdo got https://github.com/MythTV-Themes/Childish done for us |
| [02:17:53] | ** sphery was just his puppet (he spent 3x as long teaching me to do it than it would have taken him to do it :) ** | |
| [02:18:00] | Captain_Murdoch: | might be best to ask if he wants us to just become the primary repo under MythTV-Themes |
| [02:18:12] | sphery: | yeah, makes sense |
| [02:18:35] | sphery: | Also offer him privileges on MythTV-Themes/Mythbuntu, right |
| [02:19:08] | Beirdo: | we can do the same for Childish's author on that new repo :) |
| [02:19:46] | sphery: | I think that would be mag0o_ ... |
| [02:20:28] | Captain_Murdoch: | yes. |
| [02:20:54] | Beirdo: | should I delete MythTV-Themes/themes? |
| [02:20:56] | Beirdo: | it's empty |
| [02:20:57] | Captain_Murdoch: | and if others want to move their themes under MythTV-Themes, then that's fine by me as well. |
| [02:21:10] | Captain_Murdoch: | yeah. that was just a placeholder so it wasn't emtpy |
| [02:21:19] | sphery: | mag0o_: ^^^ We've moved Childish to https://github.com/MythTV-Themes/Childish , and will be granted commit/push privileges on the repo to the "maintainer(s)". That can be you and/or anyone else you can find to help you (or, if you don't want permissions--want to abandon the theme--we can see what we can do about finding someone) |
| [02:21:50] | Beirdo: | done |
| [02:21:55] | sphery: | in other words, with the repo where it is, now, we can actually give a "team" of themers privileges on it |
| [02:22:05] | sphery: | so feel free to start recruiting! :) |
| [02:22:56] | Beirdo: | jpabq: that goes for your new theme too if you want it in that spot :) |
| [02:23:33] | sphery: | jpabq: yes... Steppes could be there or in a repo you "manage" yourself or whatever is easiest for you |
| [02:23:46] | jpabq: | Beirdo, that is fine with me. Although I don't know if I am ready to give up control of it — yet. |
| [02:24:05] | Beirdo: | well, it could live there with only you having commit access too |
| [02:24:16] | Captain_Murdoch: | my packaging script also suports branches, so a themer can have a 0.24 or 0.24-fixes branch as well as master. |
| [02:24:18] | Beirdo: | completely up to you |
| [02:25:08] | Beirdo: | there's a handful of us with repo admin perms, other than that, we can customize the teams however the maintainer of each theme desires |
| [02:25:09] | jpabq: | Beirdo, right now, Steppes is at git://http://github.com/jpoet/Steppes.git . |
| [02:25:11] | Captain_Murdoch: | having them all under MythTV-Themes makes it easier for other themers to go browsing around for examples/reference. |
| [02:25:53] | Beirdo: | cool. No rush anyways, just so ya know it's available :) |
| [02:25:55] | sphery: | Captain_Murdoch: yeah, we kept 0.23-fixes and 0.24-fixes branches for Childish |
| [02:25:56] | jpabq: | For the moment, I would like to limit commit access, but I am fine moving it. |
| [02:27:30] | Beirdo: | we can easily move it at any time, so no biggie. |
| [02:27:43] | jpabq: | Do you need me to do anything? |
| [02:28:00] | Beirdo: | nope |
| [02:28:15] | sphery: | yeah, and Beirdo is amazing with git--he can make it do anything, so it's easy... I'm about to enjoy the dinner he made git cook for me. |
| [02:28:17] | Beirdo: | what I'd do would be clone, then push it back to the other repo |
| [02:28:19] | jpabq: | I believe github only allows one "private" repo, so moving it would allow me to use *my* space for something else. |
| [02:28:46] | Beirdo: | that one's set as private? |
| [02:28:52] | sphery: | hehe, now you're just being greedy ;) |
| [02:29:03] | Beirdo: | you can have more than one repo in your space though :) |
| [02:29:05] | sphery: | I think he means "personal"? |
| [02:29:12] | jpabq: | yeah, personal. |
| [02:29:35] | jpabq: | I got the impression, that if you wanted more than one personal, that they wanted money. |
| [02:29:37] | Beirdo: | I have 11 public and 0 private in mine :) |
| [02:29:55] | jpabq: | Guess I misunderstood. |
| [02:30:30] | jpabq: | Anyway, feel free to clone it into the myth tree at anytime. |
| [02:30:49] | jpabq: | Just let me know when you do, so I switch to updating the right one. |
| [02:30:58] | Beirdo: | K :) When we do, we'll set it to only you with commit |
| [02:31:10] | jpabq: | Thanks. |
| [02:31:12] | sphery: | if you like, I can do it right now |
| [02:31:25] | sphery: | I think it should be very quick |
| [02:31:28] | jpabq: | Go for it. |
| [02:31:31] | Beirdo: | it would be, yeah |
| [02:31:33] | sphery: | (except for my slow upstream bandwidth :) |
| [02:31:41] | Beirdo: | clone, add a remote, push |
| [02:32:06] | Captain_Murdoch: | the fixes/0.24 branch in the Childish repo actually has Arclight, Childish, Graphite, Mythbuntu, and metallurgy in it. |
| [02:32:20] | Beirdo: | you sure? |
| [02:32:22] | ** Captain_Murdoch was wondering why it took solong to download. ** | |
| [02:32:27] | Captain_Murdoch: | yeah, browsing on github now. |
| [02:32:48] | Beirdo: | hehe, how odd, OK, it will get fixed |
| [02:32:48] | sphery: | may get more practice, then |
| [02:33:34] | sphery: | Beirdo: so maybe I needed to git checkout first, then filter-branch? |
| [02:34:32] | sphery: | or since it's filter /branch/, maybe I need to filter for each branch? |
| [02:35:29] | Beirdo: | hmm |
| [02:35:32] | Beirdo: | yeah |
| [02:36:09] | Beirdo: | Captain_Murdoch: can you add me to owners on MythTV-Themes? Seems only owners can create more teams |
| [02:36:24] | Captain_Murdoch: | I thought you were, sure, gimme a sec... |
| [02:36:36] | Beirdo: | I am on MythTV, not on MythTV-Themes :) |
| [02:37:06] | Captain_Murdoch: | ok, you and sphery have been added. |
| [02:39:25] | Beirdo: | Cool, thanks. |
| [02:42:19] | Beirdo: | OK, created a "Commit-Steppes" team with push, pull and admin access to Steppes |
| [02:42:41] | Beirdo: | actually, should make an Admin-Steppes with the admin |
| [02:42:53] | Beirdo: | which would be jpoet (so he can add people himself) |
| [02:43:51] | Beirdo: | in theory at least |
| [02:44:10] | Beirdo: | if it won't let him, we'll do it anyways :) |
| [02:47:54] | sphery: | Captain_Murdoch: OK, Childish is fixed... You'll need to re-clone, though (much smaller this time, though--only about 5MB :) |
| [02:49:35] | Captain_Murdoch: | not trying to nitpick, but I wonder about making them Steppes-Admin and Steppes-Commit. does the team list sort alphabetically? |
| [02:50:00] | Captain_Murdoch: | sphery, thanks. verified I can re-package 0.24 and master versions of Childish. |
| [02:50:16] | Beirdo: | oooh, good idea. nitpick away |
| [02:50:19] | Beirdo: | better now than later |
| [02:50:32] | Captain_Murdoch: | which reminds me, after 0.25, I need to fix that so these are called 'master' instead of trunk on the download site. |
| [02:51:05] | Captain_Murdoch: | currently filenames have _trunk.zip and ThemeChooser class translates master -> trunk. |
| [02:51:16] | sphery: | yes, much better to get things done right before people are using this... after all, it was nice only having to tell one person (you) to re-clone after I messed up the first repo for Childish :) |
| [02:51:32] | Beirdo: | There |
| [02:51:46] | Beirdo: | teams renamed |
| [02:53:26] | Captain_Murdoch: | so, any thoughts on MythTV-Themes/Childish/Childish/themeinfo.xml vs MythTV-Themes/Childish/themeinfo.xml |
| [02:54:15] | Captain_Murdoch: | so theoretically you could also have MythTV-Themes/Childish/Childish-wide/themeinfo.xml or is it best to keep that in its own repo |
| [02:56:53] | Beirdo: | I would think it's likely better to keep separate, but I guess that might lead to more duplication |
| [02:57:43] | Beirdo: | be less confusing though |
| [02:58:42] | sphery: | jpabq: https://github.com/MythTV-Themes/Steppes . You can use your existing repo (no need to re-clone or anything) and keep any in-progress/stashed/locally-committed changes or whatever by running (in your current repo) the command: git config remote.origin.url git@github.com :MythTV-Themes/Steppes.git |
| [03:00:09] | sphery: | jpabq: Also, I only saw a master branch, so that's all I pushed up there. Please let us know if I missed anything. |
| [03:00:16] | jpabq: | sphery, so "git config remote.origin.url git@github.com :MythTV-Themes/Steppes.git" would be for when I want to push out a new version for everyone? |
| [03:00:33] | jpabq: | sphery, yup, just the one branch |
| [03:00:45] | Beirdo: | that would switch it so all pulls/pushes are to that new repo |
| [03:00:55] | jpabq: | Ah. Okay. |
| [03:01:04] | sphery: | jpabq: you just run that once and then it's as if you had originally done: git clone git@github.com :MythTV-Themes/Steppes.git |
| [03:01:14] | sphery: | (seems Beirdo is faster at answering, too :) |
| [03:01:17] | jpabq: | Got it. Thanks. |
| [03:02:03] | Beirdo: | neat concept, BTW. :) I always like having more choices around |
| [03:02:16] | Beirdo: | wish I had the artistic design bent in me |
| [03:02:18] | Captain_Murdoch: | ok, I'm fine with keeping them separate. allows finer grained control if we want. |
| [03:02:57] | jpabq: | Beirdo, Heh, not to much "art" there. Pretty much just stuck with what shapes allowed me to do. |
| [03:03:15] | Beirdo: | nothing wrong with that |
| [03:03:30] | Beirdo: | I am still toying with an ncurses-looking theme |
| [03:03:40] | Beirdo: | the concept of it anyways |
| [03:03:45] | Beirdo: | for the real retro look |
| [03:04:13] | Beirdo: | I think it would have limited use :) |
| [03:05:14] | Captain_Murdoch: | ok, verified I can re-package Steppes |
| [03:05:27] | Beirdo: | sweet |
| [03:05:39] | Beirdo: | I'm gonna get on a bus and go home, I think |
| [03:05:46] | sphery: | thanks for the help Beirdo |
| [03:05:51] | jpabq: | Captain_Murdoch, thanks. |
| [03:05:56] | Beirdo: | No problem |
| [03:07:22] | Captain_Murdoch: | sphery, just let me know if/when you move Mythbuntu and I'll update my script and test that. |
| [03:07:51] | sphery: | stuartm: BTW, if you want Metallurgy in MythTV-Themes, we can do that, too (same with your new theme). Or, feel free to manage your own repo somewhere. |
| [03:08:11] | sphery: | Captain_Murdoch: will do. I'm writing Gary an e-mail, now. |
| [03:08:48] | Captain_Murdoch: | metallurgy is gone,it's not up to date so he removed it from git and I removed it from the downloader for master. |
| [03:10:16] | sphery: | yeah, didn't know if he wanted to put it in there and then try to recruit some maintainers to help bring it up to date/maintain it. :) |
| [03:16:59] | Captain_Murdoch: | might want to do something like copy it to an 'Archives' repo because if we delete MythTV/myththemes, then we won't have any record of metallurgy anymore. |
| [03:21:40] | sphery: | That makes sense. I'll see what stuartm says (don't know if he's kept a local copy). Though I suppose filtering out non-Metallurgy stuff makes sense for the copy he keeps, anyway... |
| [04:03:42] | sphery: | Captain_Murdoch: do you know where "upstream" is for LCARS? Gary wanted to put that one in, too. And, btw, I'm moving Mythbuntu, now. (Should be done in 10min or so) |
| [04:05:17] | Captain_Murdoch: | the only place I've ever got LCARS from is the tarball on our website, I don't think it was in any repo. |
| [04:05:53] | Captain_Murdoch: | my package script is pointed at that tarball although it is never updated to need repackaging. |
| [04:06:08] | sphery: | ok, thanks... I'll offer help moving it from another repo, then, in my reply |
| [04:06:08] | Captain_Murdoch: | http://www.mythtv.org/themes/LCARS.tar.gz |
| [04:06:53] | Captain_Murdoch: | I think that was only 0.23 compatible though, so Idon't have it setup for download on 0.23, only for master in hopes someone would update it. |
| [04:07:12] | Captain_Murdoch: | s/on 0.23/on 0.24/ the theme downloader wasn't in 0.23. |
| [04:07:26] | sphery: | ok... perhaps he'll get it updated and maybe even find some people to help maintain it :) |
| [04:22:51] | Captain_Murdoch: | tested re-packaging of Mythbuntu successfully |
| [04:23:00] | sphery: | cool |
| [04:23:42] | sphery: | He also asked me to merge in the 2 commits he has on his fork--I'm currently just waiting for Beirdo to find the best way to do that. |
| [04:26:10] | sphery: | I'm starting to worry that Beirdo may have more of a life than I do. :) |
| [04:30:13] | Captain_Murdoch: | if you do merge in those, bump the theme version number as well so people will get notified of the update when I repackage. |
| [04:34:38] | sphery: | ok |
| [04:35:25] | Captain_Murdoch: | thanks. |
| [05:11:44] | Beirdo: | heh |
| [05:11:57] | Beirdo: | I decided to have a nice dinner on the way home |
| [06:25:28] | sphery: | Captain_Murdoch: OK, I merged in Gary's 2 commits (and they contained a version bump), so MythTV-Themes/Mythbuntu is ready to go. |
| [06:30:14] | sphery: | Captain_Murdoch: Also, I assume we're going to "invite" other themers to move their repos to MythTV-Themes? Would you like to make the formal announcement/invitation on -theming list or want me to? (And if you do, please mention that I'm glad to help them get their repos moved, making sure we retain history. Now that Beirdo has taught me, I'll be able to help any of them (at least those coming from git :).) |
| [06:30:55] | Beirdo: | and I'll be around to lend a hand as needed too |
| [10:45:02] | natanojl (natanojl!~jonatan@c83-252-237-63.bredband.comhem.se) has joined #mythtv-theming | |
| [13:43:49] | knightr (knightr!~knightr@mythtv/developer/knightr) has quit (Ping timeout: 248 seconds) | |
| [13:44:03] | knightr (knightr!~knightr@mythtv/developer/knightr) has joined #mythtv-theming | |
| [17:07:33] | natanojl (natanojl!~jonatan@c83-252-237-63.bredband.comhem.se) has quit (Ping timeout: 248 seconds) | |
| [20:44:15] | stuartm (stuartm!~stuartm@mythtv/developer/stuartm) has quit (*.net *.split) | |
| [20:44:15] | brfransen (brfransen!~brfransen@64.179.142.146) has quit (*.net *.split) | |
| [20:44:20] | jpabq (jpabq!~jpabq@mythtv/developer/jpabq) has quit (*.net *.split) | |
| [20:45:25] | stuartm (stuartm!~stuartm@mythtv/developer/stuartm) has joined #mythtv-theming | |
| [20:45:25] | brfransen (brfransen!~brfransen@64.179.142.146) has joined #mythtv-theming | |
| [20:45:25] | jpabq (jpabq!~jpabq@mythtv/developer/jpabq) has joined #mythtv-theming | |
| [20:45:25] | Mode for #mythtv-theming by pratchett.freenode.net : +v stuartm | |
| [21:41:09] | sphery: | stuartm: By the way, did you see the plan for MythTV/myththemes repo? We've moved Childish and Mythbuntu (and all their history--but only their history) into separate repos at https://github.com/MythTV-Themes . The only other mythui themes that were in myththemes repo were metallurgy, Arclight, and Graphite. If you'd like, I filter all the metallurgy history out of myththemes repo and either set it up on MythTV-Themes (as its own ... |
| [21:41:15] | sphery: | ... repo or as an "archived" repo) or just give you a "cut-down" copy in a tarball for safe keeping (maybe on alcor and your system). |
| [21:41:43] | sphery: | If we put it in MythTV-Themes, you might be able to recruit some users to become team members (and grant them push/pull privileges) so they can help update it. |
| [21:43:25] | stuartm: | sphery: I'm aware of it, but I've not been following the discussion, I don't mind you putting metallurgy in the repo but I don't expect to spend any time on it myself |
| [21:45:17] | stuartm: | it was designed within the limits of the old UI, working on that was what pushed me into re-writing the UI in the first place so I see it as a something of a dead end – if people like it enough then I'd be happy(ish)* for them to work on it |
| [21:45:56] | sphery: | OK, for now, I'll put it in a separate repo in there, and maybe put something in the README saying that it's out of date and needs updating. I'm planning to send an e-mail to -users list, eventually, explaining the new repo and the fact that it's set up to allow teams of users to get involved in maintaining the themes they use (where desired by authors), and will see if we can get someone interested in picking it up. If not, we can ... |
| [21:46:03] | sphery: | ... eventually move it to an archived area or something. |
| [21:46:35] | stuartm: | * I'd probably have to bite my tongue, it's difficult to see a theme get re-interpreted by someone else :) |
| [21:47:11] | sphery: | yeah, if you'd prefer, I can just give you a tarball copy for just in case, and then you can let reinterpretations happen based on recollection/screenshots/... |
| [21:48:31] | sphery: | I completely agree that artistic endeavors are fundamentally different from coding--and there's good reason for an artist to keep others from reinterpreting his vision |
| [21:48:35] | stuartm: | sphery: I've got a backup copy already |
| [21:49:21] | sphery: | Yeah, I was just thinking a backup of metallurgy with only its history (and not the rest of myththemes) might be easier, but since a full tar.gz of myththemes is only about 60MB, it's up to you |
| [21:49:43] | sphery: | I'd guess metallurgy would be about 5–10MB |
| [21:49:44] | stuartm: | I still say put it in the repo, if it doesn't attract any attention after a few months we can drop it instead |
| [21:49:50] | sphery: | ok |
| [21:49:53] | sphery: | good plan |
| [21:50:18] | sphery: | and, then again, you /can/ still have veto power over changes to it, even if you're not working on it |
| [21:50:19] | stuartm: | I've got my own local svn repo with a full history of metallurgy |
| [21:50:43] | sphery: | ah, ok |
| [21:51:12] | stuartm: | sphery: veto means reviewing changes and I'd rather not have that distraction from working on code or newer themes |
| [21:52:22] | sphery: | but it's your theme, so you'll be the one who "interviews" prospective team members and decides who can work on it, so might be able to discuss a creative vision to make sure you're on the same page |
| [21:53:08] | sphery: | anyway, I'll get it set up "soon" and we'll see what happens. thanks for the info |
| [21:55:32] | sphery: | stuartm: BTW, the approach we're using is just putting the actual theme into the top directory of the repo. The benefit is a maintainer can just clone it directly into ~/.mythtv/themes and work in the same location that mythtv is using the theme and allows very fine-grained control over permissions. The downside is it means separate themes are in separate repos, even if a themer is working on multiple themes. Think that's a good ... |
| [21:55:38] | sphery: | ... approach? |
| [22:00:14] | stuartm: | I think being able to refer to the xml of other themes can be useful, especially for those learning how to create a theme and achieve certain effects, that's much easier/faster to do when all the themes are local so that's definitely an argument for making it possible to grab all themes with a single clone |
| [22:00:53] | stuartm: | but as you note there are benefits to doing it the other way around too |
| [22:01:51] | stuartm: | for someone working on multiple themes, yes it might get a bit tiresome having to cd between each cloned repo to run git pull on each in turn |
| [22:20:52] | wagnerrp: | you can do nested git repositories |
| [22:21:01] | wagnerrp: | but to be honest, there is really little benefit in doing so |
| [22:39:54] | sphery: | stuartm: metallurgy is up there, now ( https://github.com/MythTV-Themes/metallurgy ). Do you want to update readme or want me to? |
| [22:40:41] | stuartm: | sphery: if you don't mind :) |
| [22:43:11] | sphery: | OK. How about just adding this to the top: This theme is out of date and does not work with current MythTV. Please contact Stuart Morgan at the address listed in themeinfo.xml if you would like to volunteer to help update and maintain the theme. |
| [22:44:01] | natanojl (natanojl!~jonatan@c83-252-237-63.bredband.comhem.se) has joined #mythtv-theming | |
| [22:47:40] | sphery: | I'm going with that for now. Feel free to modify (or ask me to) if desired. |
| [23:04:43] | natanojl (natanojl!~jonatan@c83-252-237-63.bredband.comhem.se) has quit (Ping timeout: 260 seconds) | |
IRC Logs collected by
BeirdoBot.
Please use the above link to report any bugs.