sharpetronics/geany
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added a missing word and some smaller changes on spelling (GitHub; pull request)

Browse Source
This commit is contained in:
Frank Lanitz 2012-05-31 22:33:07 +02:00
parent 54ed2189fe
commit 7b339b8d30
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/geany.txt
View File

@ -5000,7 +5000,7 @@ After you are happy with your changes, create a patch e.g. by using::
and then submit that file to the mailing list for review. and then submit that file to the mailing list for review.
Also you can clone the Geany at github and send a pullrequest. Also you can clone the Geany repository at GitHub and send a pull request.
Note, you will need the Python docutils software package installed Note, you will need the Python docutils software package installed
to build the docs. The package is named ``python-docutils`` on Debian to build the docs. The package is named ``python-docutils`` on Debian

4
doc/plugins.dox
View File

@ -85,7 +85,7 @@
* @subsection code Managing the source code * @subsection code Managing the source code
* *
* For authors of plugins for Geany, we created a dedicated @a geany-plugins using * For authors of plugins for Geany, we created a dedicated @a geany-plugins using
* project Sourceforge and github to ease development of plugins and help new authors. * project Sourceforge and GitHub to ease development of plugins and help new authors.
* All information about this project you can find at http://plugins.geany.org/ * All information about this project you can find at http://plugins.geany.org/
* *
* To add a new plugin to this project, get in contact with the people at * To add a new plugin to this project, get in contact with the people at
@ -96,7 +96,7 @@
* However, once you have done your fork of geany-plugins you can develop * However, once you have done your fork of geany-plugins you can develop
* your plugin until you think its the right time to publish it. At this point create a * your plugin until you think its the right time to publish it. At this point create a
* pull request for adding your patch set into master branch of geany-plugins. * pull request for adding your patch set into master branch of geany-plugins.
* Of course, you don't need to use github - just any Git is fine. But github * Of course, you don't need to use GitHub - just any Git is fine. But GitHub
* is making it way easier for review, merging and get in touch with you for * is making it way easier for review, merging and get in touch with you for
* comments. * comments.
* *