Hello > The best reference for git I've found is the Pro Git book: > > http://git-scm.com/book
Thanks, great source; I understood its main goals and basic usage. > Basically what you want to do is clone the central git repo, create a new > local branch (maybe call it general-mechatronics-driver?), add the files for > your driver, add a manpage and whatever other docs you want, maybe add a > sample config, then publish that branch somewhere (github offers free git > hosting). > I added driver and documentation to github: https://github.com/BenceKovacs/linuxcnc-mirror I hope I did everything fine. > Then the other devs can look at it and offer feedback, and we can push it to > the central repo to have our buildbot test it. We are waiting for your feedback. We are making and testing sample configurations. It takes a few days to make sure they are working fine. I will push it to the same place. Thank you in advance for reviewing our code. Bence 2012/10/1 Sebastian Kuzminsky <s...@highlab.com>: > On Oct 1, 2012, at 09:48 , Bence Kovács wrote: > >> Sebastian: >> Thanks for help and review, I attach the code. We used mostly FPGA >> firmware and schematics of our previous robot controller which boots >> from serial eeprom (it was not PC based). So it is ‘hard wired’, not >> reconfigurable, so we didn't make it open source. >> I am sure I will need some help with git. Is it a more detailed howto >> somewhere? > > > There's our brief intro here, which includes some links to other tutorials: > > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Git > > > The best reference for git I've found is the Pro Git book: > > http://git-scm.com/book > > > For me the key to understanding git was to understand the logical > relationships between the different kinds of objects: repos, branches, > commits, files & directories, and the index (aka the staging area). Once > that was all clear, the git commands all made sense. Study the documentation > and feel free to ask specific questions here. > > Basically what you want to do is clone the central git repo, create a new > local branch (maybe call it general-mechatronics-driver?), add the files for > your driver, add a manpage and whatever other docs you want, maybe add a > sample config, then publish that branch somewhere (github offers free git > hosting). > > Then the other devs can look at it and offer feedback, and we can push it to > the central repo to have our buildbot test it. > > > -- > Sebastian Kuzminsky > > > ------------------------------------------------------------------------------ > Got visibility? > Most devs has no idea what their production app looks like. > Find out how fast your code is with AppDynamics Lite. > http://ad.doubleclick.net/clk;262219671;13503038;y? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
