the only logical answer is they are near the push broom as I cannot find it either.
so much for that theory... I found the ferrules but the broom is still MIA
the idea is that you always find the thing you aren't looking for, so looking for the brom was the answer
I still haven't found the broom LOL
EMC: 03jepler 07master * rf6432d2ca07a 10/ (119 files in 11 dirs): move hostmot2 firmwares to the hostmot2-firmware project
* [new branch] v2.4_branch -> v2.4_branch
It's my pleasure to announce the opening of the v2.4_branch, and the reopening of master for new features.
PCW_ is now known as PCW
WEEE! a new branch!
jepler: do you know if the docs can be edited from 8.04 lyx for both 2.4 and dev?
jt-plasma: the same lyx you were using yesterday to edit master is the same one you should use today for 2.4 and master
jt-plasma: we might evaluate whether to use the 10.04 lyx during development towards 2.5, though.
ok, just let me know
EMC: 03jepler 07master * r68a3312b5a44 10/ (VERSION debian/changelog): bump master to start the development of new features in the 2.5 series
documentation for 2.4: http://linuxcnc.org/docs/2.4/html/
docs/devel will track master, as expected
I'll work on the debian/changelog later tonight
should I put that link on the docs page at linuxcnc.org as the soon to be released version?
* jt-plasma wanders inside to see about some chow, that piece of toast for breakfast is getting thin
jt-plasma: I'd hold off linking it more prominently for now
now, was there anything else I needed to tell the mailing list about?
git log --oneline --since="April 20, 2009" | wc -l
^^ number of commits I have to at least glance at to make the debian/changelog
I'm glad I'm not helping for another month or two :)
wow that's a big number.
our project - it is vibrant
who can tell me whether NURBS are useful enough to be left in?
iirc it had problems like violating constraints
I don't think they're useful in their current state.
(but, I'm not sure taking them out is smart at this late date)
hm, how much detail to put in debian/changelog?
do you think we've gotten it wrong previously?
it's just so tempting to write one line for each commit
I won't go quite that far
jepler: is there any value to tagging the 2.4 branch point, so we know where to start our feature branches?
I guess we can always use merge-base to find it