I'm not at all against long running branches of development. I have two myself (which I need to finish and pull request!) I propose that these could be moved to personal github accounts and merged later when ready. In the end removing these tags from the main repository and putting them into parallel github accounts helps separate concerns and reduces confusion about what is going on in linuxcnc.
My clone of linuxcnc has so many branches that I dont know what they are for. I think in general all if these branches end up functioning as noise to most people. (not saying that they don't contain useful changes) but in that case why arent we discussing on the dev list and pulling changes into master.... 2 semantic cents is all I have to offer here... :-) -Curt On Sun, Aug 1, 2021, 2:21 PM andy pugh <bodge...@gmail.com> wrote: > On Sun, 1 Aug 2021 at 19:09, Curtis Dutton <curtd...@gmail.com> wrote: > > > Github makes having these branches in the linuxcnc git uneeded. Arent > these > > extraneous branches holdovers from the time that linuxcnc was self > hosting > > a git server? > > Some contain work-in-progress that has not made it into the main branches. > > As an example I was reminded today of a branch I made that has the BBB > PRU drivers in it. But it was never tested so I didn't feel that it > should be merged. > > -- > atp > "A motorcycle is a bicycle with a pandemonium attachment and is > designed for the especial use of mechanical geniuses, daredevils and > lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1912 > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
