#linuxcnc-devel | Logs for 2016-10-29

[01:32:32] <seb_kuzminsky> https://www.youtube.com/watch?v=LSm1yFQv6QM
[04:56:35] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15tseufl opened issue #207: website: new forum template -> missing link + wrong favicon 02https://github.com/LinuxCNC/linuxcnc/issues/207
[08:43:07] <jepler> I am getting tired of bugs filed about things with zero impact on meat humans
[08:43:19] <jepler> (at the same time I am sure tseufl means well)
[08:44:08] <jthornton> bugzilla?
[08:45:05] <archivist> they do have an effect on humans too
[09:25:02] <jepler> yes I mean obviously it makes certain meat humans complain
[09:30:28] <jepler> the forum is a fucking albatross that I really don't care to maintain
[09:30:37] <jepler> but of course nobody else will actually do it so here I am stuck doing it
[09:31:23] <jepler> so it pisses me off when people drive by and say "that favicon offends me" because it ignores that I really spend quite a bit of effort to provide something our users get a lot of benefit from
[09:31:29] <jepler> and I am feeling thin skinned this morning
[09:31:45] <jepler> at least tseufl has filed some useful pull requests
[09:32:13] <jepler> .. I'll just go over there -------> and try to simmer down, sorry for the outburst.
[09:36:32] <archivist> it is kind of hard to help if we get chewed at
[13:34:03] <KGB-linuxcnc> 03Norbert Schechner 052.7 cecf5fd 06linuxcnc 10src/emc/usr_intf/gmoccapy/getiniinfo.py 10src/emc/usr_intf/gmoccapy/gmoccapy.py 10src/emc/usr_intf/gmoccapy/release_notes.txt gmoccapy_1_5_6_7 - subroutine bug solved * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=cecf5fd
[13:47:39] -linuxcnc-github:#linuxcnc-devel- [13linuxcnc] 15gmoccapy commented on issue #207: I do miss also a link to mark all topics read.... 02https://github.com/LinuxCNC/linuxcnc/issues/207#issuecomment-257107257
[13:55:36] <KGB-linuxcnc> 03Norbert Schechner 052.7 5ae809b 06linuxcnc 10src/emc/usr_intf/gmoccapy/getiniinfo.py gmoccapy_get_ini_info - cosmetic and doble entry * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=5ae809b
[16:29:12] <KGB-linuxcnc> 03Kim Kirwan 05master 1a17b51 06linuxcnc 10debian/configure Improve support for Mint 18 (LTS) * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1a17b51
[18:39:23] <KimK_laptop> If I have a reference like "1:2.8.0~pre1.2239.gb97a1ca" to go back to, do I want to say "git checkout b97a1ca? I did that and it seemed to work, but it says I'm in "detached head" state. Is that OK? Is that what I want (to build an old version)?
[18:40:15] <KimK_laptop> I've got to go now, but please post any advice and I'll be back later tonight to see it. Thanks in advance!
[19:29:52] <seb_kuzminsky> KimK_laptop: yes, you can checkout the part after the "-g" to get exactly what when into that version of the debian package
[19:30:59] <seb_kuzminsky> you'll be in a "detached head" situation, which means "not on a branch"
[19:31:18] <seb_kuzminsky> if you just want to run tests or see what things were like back then, a detached head is fine
[19:31:52] <seb_kuzminsky> if you want to make commits (for example, to add a test and/or fix a bug), you'll want to create a new branch at that commit
[19:32:21] <seb_kuzminsky> you can do this after entering a detached head state by just saying "git branch my-new-branch", it'll start out pointing at whatever commit you have checked out when you run the command
[19:32:59] <seb_kuzminsky> another way to do it, without entering the detached head state, is to say "git branch my-new-branch b97a1ca", then "git checkout my-new branch"
[19:33:32] <seb_kuzminsky> that'll do the same thing, but because you created the branch (at the specified commit) and then checked out the branch (instead of the commit), you'll be on a branch, not in a detached head state
[19:33:36] <seb_kuzminsky> clear as mud?
[20:27:46] <andypugh> It made sense to me. And that’s not common with Git.
[20:46:26] <skunkworks_> zlog