Oh, got it:

https://guide.macports.org/chunked/project.update-policies.html

Port maintainers normally are given commit privileges to the Subversion 
repository so they can make updates to their own ports as described in Section 
7.4, “MacPorts Membership” 
<https://guide.macports.org/chunked/project.membership.html>. However, The 
MacPorts Project does not restrict commit privileges for maintainers, so before 
a person other than a port's maintainer updates a port it is a good practice to 
inform a port's maintainer. See details below.

…do you have commit privileges, or can you ask for it? this will speed up 
things dramatically…

Emanuel

> On Sep 30, 2016, at 3:16 PM, MacPorts <nore...@macports.org> wrote:
> 
> #52462: ALPSCore version update to 0.5.5
> -----------------------+----------------------
>  Reporter:  egull@…   |      Owner:  galexv@…
>      Type:  update    |     Status:  new
>  Priority:  Normal    |  Milestone:
> Component:  ports     |    Version:
> Resolution:            |   Keywords:  haspatch
>      Port:  ALPSCore  |
> -----------------------+----------------------
> Changes (by mf2k@…):
> 
> * owner:  macports-tickets@… => galexv@…
> * cc: galexv@… (removed)
> * version:  2.3.4 =>
> 
> 
> Comment:
> 
> Please do not modify the {{{# $Id:}}} line. It may mean you have edited on
> old version of the Portfile.
> 
> -- 
> Ticket URL: <https://trac.macports.org/ticket/52462#comment:1>
> MacPorts <https://www.macports.org/>
> Ports system for the Mac operating system

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to