Lerman: heh - no. You just let the cat out of the bag. (git) :)
Nope. Not me. If you want to keep the cat in the bag, don't put it in the Wiki.
[00:41:11] <lerman_> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?BoardOfDirectors
note that the motion was "prepare a message to the list"
we were still doing that when you mentioned (on the list) that we want to go to git
Sorry. When I read it on the wiki, I assumed that it would be OK to discuss it.
it wasn't a secret, but we wanted to announce it correctly (with justifications etc) which is now done
no harm done whatsoever
no harm done - it prompted us to quit editing the message and send it already
So... Should I create a CVS repository or use git or wait?
I don't know the answer to that.
Do we have someone who can guess better than I can?
"wait" is the simplest choice - least chance of doing something over
but I don't know how long you are willing to wait
I can do that. I'll just create a package and let people download it from my site if they want it. I don't think anyone else will want to modify it in the short term.
lerman_: I think it would be a great opportunity to learn a bit of git
if putting gwiz in cvs means learning cvs you don't know today, then I'd say that's another reason to do it in git
EMC: 03seb 07v2_3_branch * 10emc2/configs/hm2-servo/hm2-servo.hal: Use the [AXIS_?]INPUT_SCALE value from the .ini as the encoder scale, instead of hardcoding it in the .hal.
EMC: 03cmorley 07TRUNK * 10emc2/src/emc/usr_intf/pncconf/pncconf.py:
EMC: fix conversion of pwm from gpio on gui
EMC: fix flood, spindle brake, spindle ccw, flood and mist signals
EMC: not being recognised/connected.
EMC: fixed pdm frequency update problems
EMC: added info to configuration readme
EMC: 03seb 07TRUNK * 10emc2/configs/hm2-servo/hm2-servo.hal: merge hm2-servo config fix from 2.3 branch: use [AXIS_?]INPUT_SCALE for encoder scale
gitty up mule
hmmm the HAL manual does not work in 2.3.1 it's on the menu but won't display
I think it's spelled HAL_User_Manual.pdf
even if I correct the menu is still won't display for some reason
if I just navigate to it and click on it it works
check the spelling and capitalization a few more times?
yep it is spelled correctly
in a terminal I get Permission denied
if you type /usr/share/doc/emc2/HAL_User_Manual.pdf as a command in the terminal it won't work. pdf files are documents, not executable programs. "/usr/bin/see" is what opens the document in the right viewer.
I typed "Exec=/usr/bin/see /usr/share/doc/emc2/HAL_Manual.pdf"
if you want to test it in the terminal, use everything after Exec=
if I copy and paste this "/usr/bin/see /usr/share/doc/emc2/HAL_Manual.pdf" into the menu launcher properties is does not work but it works from the command line
If I create a brand new launcher it works
there must be something else funky in that .desktop file, then
I wonder what it is
how can you just open the .desktop file with a plain text editor?
also if you edit menus/properties on the HAL one the icon is different than the rest of them
you should be able to open it with a text editor .. if you want to open the one in /usr then you will have to 'sudo gedit' since it is a system file not a user file
(if you want to save changes, anyway)
ok, if I edit usr/share/applications/emc2-halmanual.desktop with sudo gedit the changes work
you mean your 'git clone'? it's going to be rather brutal on a slow line.
you could clone it on a box with a fast connection and then transport it to your computer on a thumb drive or whatnot..
yea, my git clone :)
hm my arithmetic says that if it took 5 minutes on a 3 megabit line, you're in for about 5 hours
3 down 2 to go :)
after I edited the usr/share/applications/emc2-halmanual.desktop and saved it the menu worked but when I right click on the menu and edit menus my change did not show up :/
done with the walk now it is got
EMC: 03cmorley 07TRUNK * 10emc2/src/emc/usr_intf/stepconf/stepconf.py: fix second and third parport direction not being updated properly
EMC: 03cmorley 07v2_3_branch * 10emc2/src/emc/usr_intf/stepconf/stepconf.py: fixsecond and third parport direction not being updated properlt
a bash syntax I don't recall seeing before: for ((i=1;i<10;i++)); do echo $i; done
EMC: 03cmorley 07v2_3_branch * 10emc2/debian/changelog: update changelog about fix. Hope it in the right spot-easy to fix
EMC: 03jepler 07v2_3_branch * 10emc2/debian/changelog: proper format for debian/changelog
jmkasunich: at fest you showed me a diagram of how emc makes motion happen - is it in our CVS or on the web somewhere?
seb_kuzminsky: on the web
url in a sec
[19:41:41] <jmkasunich> http://jmkasunich.com/pics/emc2-motion-dataflow.pdf
see also: http://cvs.linuxcnc.org/cvs/emc2/src/emc/motion/teleop-notes?rev=1.2
the latter has a link to the former
note that the drawing is a proposal of how things might be once we get joints and axes properly separated, and teleop working
it is not quite what we have now
i found something similar that will work for me: http://www.linuxcnc.org/docs/2.3/html/code_Code_Notes.html#r3_2
that one is a more accurate representation of what we have now
the Code Code Notes doesnt show how the homing logic informs the joint controller's motor offset, but other than that it's good
EMC: 03bigjohnt 07TRUNK * 10emc2/debian/extras-Ubuntu-6.06/usr/share/applications/emc2-halmanual.desktop: fix hal user manual spelling in .desktop
EMC: 03bigjohnt 07TRUNK * 10emc2/debian/extras-Ubuntu-8.04/usr/share/applications/ (emc2-gettingstarted.desktop emc2-halmanual.desktop): fix hal user manual spelling in .desktop
BigJohnT_ is now known as BigJohnT
EMC: 03bigjohnt 07v2_3_branch * 10emc2/debian/extras-Ubuntu-6.06/usr/share/applications/emc2-halmanual.desktop: fix hal user manual spelling in .desktop
EMC: 03bigjohnt 07v2_3_branch * 10emc2/debian/extras-Ubuntu-8.04/usr/share/applications/emc2-halmanual.desktop: fix hal user manual spelling in .desktop
* BigJohnT likes qgit
so did emc2 go to git?
the board would like to, and sent a proposal/statement of intent to the developers yesterday. there hasn't been any response yet.
well it took me 5 hours to download on my string :)
BigJohnT: well it'll be easy to keep up, from then on
so far it is very intutive to work with the gui
a slow connection is all the more reason to have the history information local
I see. just wondered what came from the discussion at the fest.
that's good to hear
commits using qgit are easier to see what your about to commit
[20:30:14] <cradek> http://article.gmane.org/gmane.linux.distributions.emc.devel/2247
Jeff saved Git for the Lazy for last :)
do you have to clone the branch like you did the master?
no, you never have to do the big copy again
your local repository is just as good as any other
how do I just work on a branch?
git branch --track v2_3_branch origin/v2_3_branch
git checkout v2_3_branch
I did that
ok, you're on the branch
so after doing that I change something in emc2-experimental and it is only applied to branch?
yes if you commit it will be on the branch
then you'd do a push if you want to share that change
(I don't think emc2-experimental accepts pushes right now)
* BigJohnT wanders out to the shop to paint tractor parts
right, you can't "push" back to linuxcnc.org yet
but you can make changes and "commit" them locally
seb_kuzminsky: there sure is a lot of silence about it...
programmers, et. al.: if git is a significant improvement, go for it.