On Sat, 6 Oct 2012 13:00:05 +0200
Michael Gmelin <free...@grem.de> wrote:

> Hi,
> 
> After some complications while submitting a patch to devel/py-ice
> (getting a patch containing UTF-8 characters through the PR
> system) the maintainer finally managed to apply the patch
> successfully, but also decided to give up maintainership. Since I'm
> already managing devel/ice and the two ports work closely together, I
> offered to take over maintainership.
> 
> Tony (the maintainer) wrote "Ok this all worked fine so can commit and
> make yourself maintainer, thanks!"
> ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171645#reply9 )
> 
> I'm not the maintainer yet and I don't hold any commit bits, so I
> don't think I can do any of these things myself. So what is the exact
> process at this point? I understand how this works for abandoned
> ports, but this is new to me and I couldn't find anything about such
> a process in the Porter's Handbook[1], Contributing to the FreeBSD
> Ports Collection[2] or Writing FreeBSD Problem Reports[3].
> 
> Thanks,
> Michael
> 
> 1.
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> 2.
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/article.html
> 3.
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html
> 

Hi,

Sorry to bother the list about this again, but I would really like to
finish upgrading the port - since the maintainer is really short in
time this got kind of stuck in the middle. He's fine with passing on
maintainership and also with the patch - if the PR is too messy for a
committer (there were a couple of - unresolved - encoding issues) I
would suggest to close it, pass maintainership to me and I will open a
new PR to get the updates in.

Thanks,
Michael

-- 
Michael Gmelin
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to