[MacPorts] #66555: Why MacPorts could consider to rename its ''master'' branch to **main**

MacPorts noreply at macports.org
Mon Dec 26 18:40:42 UTC 2022


#66555: Why MacPorts could consider to rename its ''master'' branch to **main**
-----------------------+-----------------------------
  Reporter:  Zweihorn  |      Owner:  (none)
      Type:  request   |     Status:  closed
  Priority:  Normal    |  Milestone:  MacPorts Future
 Component:  ports     |    Version:  2.8.0
Resolution:  invalid   |   Keywords:
      Port:            |
-----------------------+-----------------------------

Comment (by Zweihorn):

 THX

 I am rather neutral on this and just wanted to learn of your deliberations
 (or not). You already fully met my expectations by this friendly reply and
 kind advice. What might have looked like a simple name change at first
 could bring MacPorts ports and update process into troubled water,
 apparently.

 As the word 'master' should in no way be problematic itself the a.m.
 rationale from you is more than sufficient IMO.

 Case closed. Conversation most appreciated.

-- 
Ticket URL: <https://trac.macports.org/ticket/66555#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list