Re: Renaming branches in the Nagios Plugins repository

Holger Weiß <[email protected]>
Newsgroups gmane.network.nagios.plugins.devel
Organization Freie Universität Berlin
Message-ID <[email protected]>
* Holger Weiß <[email protected]> [2012-06-25 16:59]:
> I'd like to rename the branches in the Nagios Plugins repository in
> order to make their current state a little more obvious.
> (Unfortunately, we cannot simply delete the dead topic/maintenance
> branches, as they weren't properly merged into the master branch.)
> 
> I'd suggest the following names:
> 
> 	OLD NAME             | NEW NAME
> 	---------------------+------------------------
> 	master               | master
> 	pu_dermoth_http      | tg/http_chunked
> 	dermoth_ntp_rework   | tg/ntp_rework
> 	new_threshold_syntax | tv/new_threshold_syntax
> 	ton/state            | archive/state_file
> 	maint-1.4.15         | archive/maint-1.4.15
> 	r1_4-patches         | archive/maint-1.4
> 	release-1.3.0        | archive/release-1.3.0
> 	avendor              | archive/avendor

Done.  You can run a command such as

	git remote update --prune

to update your local clones of the repository.

Holger

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.