[Global Notice] Hi all, We are now in the final stages of preparing the change over from hyperion to ircd-seven, we would encourage users and projects to read http://announce.freenode.net
and familiarise yourselves with upcoming migration plans, we also suggest making sure that your bots and scripts work with the new ircd. Thank you and have a good day!
EMC: 03jthornton 07master * r58aea10b28bf 10/docs/man/man1/ (comp.1 halui.1): spelling fix
EMC: 03jthornton 07master * re2a3300618a5 10/docs/src/config/ini_config.lyx: cycle time change
in inifile there are allowed comments at end of lines with variables? like name = value # comment
and comment should be ignored?
if so then we probably have bug in inifile handling
hmm docs says that 'name = value # comment' is wrong
one reason we might not want to change that is that ";" is a comment character too, but a character that is more plausibly useful in a value
such as a hypothetical new option RUN_AT_SHUTDOWN = shell command 1; shell command 2
it would be worse than now if "#" can be a comment anywhere in the line, but ";" only at the beginning
no I don't want any change
it's ok for me
Here's another not totally impossible value: RS274NGC_STARTUP = #1=100
but while working on ja3 I've noticed some configs with bad comments
now I know that they're wrong
which ones? I grepped but didn't find anything right away
[Global Notice] Hi all, we are currently experiencing a "new sort of spam" -- where the spammer claims to be tunelling via HTTP POST and encourages you to visit a url. Visiting the URL opens another connecting via YOUR ip which spams further, we encourage you to NOT click the link to avoid being banned from channels or the network. Thank you.
scara had bad ones fixed in http://git.linuxcnc.org/gitweb?p=emc2.git;a=commit;h=c0a6ece737b3813c99bf50b3fe001280dbd50713
looks like that one was introduced on the branch, never on master
if there are some that exist only on the branch then just fix them there
if they exist on master and branch, then one strategy is to fix them on master and merge master to branch; or fix on a branch started from the common ancestor and merge that to both branches
I see, thanks