Thanks for the instructions. I went ahead and submitted it that way too. For newbees like myself to using git with other projects in this way, I added some extra steps/hints.
1.5 Clone your forked repo to your local system, using the "Your Clone URL". 2.5 The changes should be done on your master branch, or merged onto it if done on another branch. I'm not sure about this, but people on github usually just work on master. 4.5 Wasn't sure if its good practice to send the Pull Request to all users who forked or just the owner. I just sent it to you and why as to not spam others especially since this is not a functional change. -mat On Thu, Jul 9, 2009 at 10:59 AM, Devyn Cairns <[email protected]>wrote: > Sure, you could do it this way. But most of the time the procedure is > > 1. Fork Shoes on Github (github.com/why/shoes) > 2. Make Changes > 3. Push to your fork > 4. Use the Pull Request feature in Github. > > On Wed, Jul 8, 2009 at 11:36 PM, Mathew Cucuzella<[email protected]> wrote: > > While reading through the on-line shoes2 manual, I noticed a > > few small errors. Attached is a git-format-patch with the > > fixes. If this isn't the right way to submit a patch, I'm happy > > to supply them in any format. > > > > Mathew Cucuzella > > http://github.com/kookjr > > > > - - - - - Environment Info - - - - - > > Ubuntu 9.04 > > shoes.run, Raisins release, Makeself version 2.1.5 > > > > > > -- > ~devyn >
