should I say thank you <duck and roll> seriously though. If you are trusted to push the documentation, we should trust you period. Nothing says you have to modify anything outside of the doc section. Why try to limit it? Other than that, a branch/merge/pull should like it work fine too.
On Jun 4 2013 11:23 PM, Kent A. Reed wrote: > Ok, so Michael has thrown down the gauntlet: "Now please stop the > damn > 'thank you' thing, and contribute something." > > Circumstances prevent me from contributing much in the way of code > but > y'all know I have a passion for decent documentation. I have made a > number of contributions to the Wiki and to the distributed LinuxCNC > documentation. > > The process I used last year to contribute to the docs was horribly > inefficient. I would first find problems, then document them as to > source file, line, and the change to be made. Then I'd fire off > emails > to John Thornton who would fire up his trusty editor and, file by > file, > line by line, first locate what I was talking about, and then make > the > corrections he agreed with (which he mostly did; thanks, John). > > Frankly, I'd rather just edit the document source files and be done > with > it. It's something I can do at odd moments during the day as I see > problems in the pdf/html results. > > I see two possibilities for doing this in an organized way: > > 1) create my own public git repository, edit and post files to it > after > pulling from the central repository, and announce their availability > to > y'all. It would then be up to 'someone' to pull them and merge them > in > the central repository. > > or > > 2) get push privilege to the central repository. It would be super if > git allowed for restriction of push privilege to the ./docs subset, > since that's all I need/want, but I'm not aware that it does. > > And the answer is...? > > Regards, > Kent > > > > ------------------------------------------------------------------------------ > How ServiceNow helps IT people transform IT departments: > 1. A cloud service to automate IT design, transition and operations > 2. Dashboards that offer high-level views of enterprise services > 3. A single system of record for all IT processes > http://p.sf.net/sfu/servicenow-d2d-j > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
