[HEADS UP] Repositories moved to Github
Holger Weiß <[email protected]>
| Newsgroups | gmane.network.nagios.plugins.devel |
|---|---|
| Organization | Freie Universität Berlin |
| Message-ID | <[email protected]> |
As nobody seemed to object¹, I moved our repositories to Github: https://github.com/nagios-plugins Contributors are now encouraged to send pull requests via Github² instead of using the "Patches" tracker on SourceForge. Please also feel free to create pull requests for unhandled patches you sent to the SourceForge tracker (but don't forget to mention the SourceForge tracker item ID in the pull request). Team members with push access will have to update their local clones of the repositories. Assuming you cloned the "nagiosplug" repository and the remote repository is referenced by the name "origin" (which it is by default), you could use the following command to update the URL: $ git remote set-url origin git-9UaJU3cA/F/[email protected]:nagios-plugins/nagios-plugins.git Anyone else can continue to track the SourceForge repositories, as they now mirror the Github repositories. We're looking forward to your pull requests :-) Holger ¹ See: http://thread.gmane.org/gmane.network.nagios.plugins.devel/7570 ² See: http://help.github.com/send-pull-requests/ ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel-5NWGOfrQmneRv+LV9MX5upmplPMkL2fr@public.gmane.orget Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null