well, to be fair, you can just edit in the web interface on git (as you have done). putting the docs on a wiki doesn't allow us to attach documentation to the versions of the software and isn't a viable solution.
On Thu, Nov 19, 2009 at 3:39 PM, Jon Hancock <[email protected]> wrote: > I'm only decent at git as a single user. I rarely do forks of other > people's works unless its critical to my work to get my fix/change > integrated. > For things like docs, I see no reason why a wiki isn't the best > choice. You make the participation barrier as low as possible and > still get manageable content. > > Jon > > On Nov 18, 12:56 am, Aaron Newton <[email protected]> wrote: > > I did get the pull request. The git command line is very, very powerful, > but > > a little daunting. Learning it though is a valuable skill if you're a > > developer. Once you get the hang of it, it's fairly easy to get a lot of > > work done. > > > > > > > > On Tue, Nov 17, 2009 at 8:19 PM, batman42ca <[email protected]> wrote: > > > Now that I've made a change, and didn't lose it this time, I also made > > > a pull-request. Can you confirm that the request was successful? > > > > > I want to help correct the documentation when I see errors, but Github > > > seems far from intuitive to me and I have no clue if I'm doing it > > > right. The only documentation I've seen on Github talks about the > > > command line, yet everything I see is done through a graphical user > > > interface. > > > > > On Nov 9, 8:37 pm, Aaron Newton <[email protected]> wrote: > > > > try looking in your network graph, which should show all your > commits. > > > click > > > > on the little green down-ward fork in the upper right corner of your > > > > project, or go here: > > > > > >http://github.com/< your user name here>/mootools-more/network > > > > > > - Show quoted text - >
