On Mar 27 2014 12:10 AM, Frank Tkalcevic wrote: >> I guess I would first ask if the licenses are compatible. >> If so, then I am sure you are good., If not, then you >> have to find a path through that minefield. > > Ouch, I never considered that. I'd hate not to be able to share back > to the > linuxcnc community.
If it is your code, then you can relicense it to be compatible. If it is not, then do everyone a favour and find another tool or write it from scratch. You would not believe the *hundreds* of hours spent on the list attempting to deal with that issue, and now that LCNC is being cleaned up I do not think that *any* of us would allow a new problem child... >> I would say you do not understand a source code repository >> (particularly git) and how that allows you to set up branches, >> forks, etc. Using git in your own >> named branch is probably the way to go... > > Absolutely. I use simple source code repositories - SVN, CVS. With > a main > trunk and branches that eventually get stitched back to the trunk - > so > really there is only one version, or a second on a branch. > > I get overwhelmed thinking about my current branch, which is 2 > versions old, > then bringing it up to date, then bringing in goodies (branches, JA4, > etc) > and how to manage that. Every text I read on GIT talks about > branches as > objects and how multiple branches just come together. > > I have asked about git on this mailing list before and been given > advice, > but I just haven't taken the plunge yet. Git has a steep learning curve. That is why in part I prefer mercurial to git -- you can do all the same things, but the basics are easier to do, and the esoterics are harder to find. It sounds like it is time for you to jump in the whitewater ;-) EBo -- ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
