Nils Bruin <[email protected]> writes: > On Jul 27, 8:45 pm, Jason Grout <[email protected]> wrote: >> To format a "patch", log into github, go to the >> file:https://github.com/sagemath/sagenb/blob/master/sagenb/notebook/intera... >> >> Click on "edit in the upper right of the file listing >> >> Make the change in the browser editor, then click "Submit pull request" > > Thanks! The amazing thing is that you describe the full process! I > didn't use github before. Sage's trac submission process is a long > string of tedium interspersed with boredom and administrative red tape > by comparison (especially for a 1 character patch).
Yup, that's a really nice thing about github's online editor. It's great for typo fixes and other trivial edits. Of course, if your patch was a bit more complicated, or touched multiple files, you'd have needed to do a bit more footwork - forking the repository on github, cloning your fork to your local computer, committing your changes, pushing them to a branch on your github fork, and then creating a pull request from your fork's new branch to the sagemath user's fork's master branch. So, not that much easier than Sage's trac submission process on first glance, though IMO once you get used to it it's really nice to not have to deal with patch files bitrotting and such. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
