Yes! Humidity is pretty bad in northern indiana also at times also
it is pretty bad here in Swamp East Missouri most of the time...
back in a minute
* JT-Hardinge gets back to making floor space from piles of stuff...
I'm sure it does....
JT-Hardinge: the sky is the limit =)
Actually the limit is the ceiling.. :-)
bbl gotta go clean up a painting job ...
ok dave911 I sent the email
jthornton are you building a machine shop?
or a hobby shop?
Dave911 email the list with comments if any > Cheers
chester88: both lol
I use the machines for both work and pleasure
much better :)
EMC: 03jepler 07master * r69f192a40417 10/src/Makefile: complete installation of gladevcp
EMC: 03jepler 07master * rc82ede900dbb 10/src/ (8 files in 4 dirs): remove execute bits that don't belong
EMC: 03jepler 07master * re7d72f893450 10/configs/plasma-thc/mp1000_serial.py.threadedNonSafe: remove file added by mistake
I have entered "git branch --track v2.4_branch origin/v2.4_branch". Do I have to also enter "git branch --track master origin/master" (or something like that), or has that happened automatically already, because master is/was the default? And these two branch selections will be remembered until changed, right?
KimK_: the 'git clone' process does the equivalent of 'git branch --track master origin/master'
jepler: OK. But I was thinking of after I have cloned. I expect to be using git/emc2-dev in both 2.4 and master, at different times for different purposes. I was wondering if (to update both branches) I have to do something like: checkout master, git pull --rebase, checkout 2.4, git pull --rebase ? Or does checkout master, git pull --rebase, adequately cover both branches?
Does git keep track seperately?
I guess is what I'm asking.
Once I have declared two branches.
* JT-Hardinge is off to dinner now
OK, thank you both.
would one of you learned and revered C programmers check this please? http://timeguy.com/cradek-files/emc/0001-skip-invalid-tool-table-entries-instead-of-crashing.patch
it tests ok, but I'm not confident enough about break/continue in that nested stuff doing strtok. It (or a correct fix) should surely go on v2.4_branch