Bug 154636 - www/mod_bandwidth change of maintainer (includes updated files)
Summary: www/mod_bandwidth change of maintainer (includes updated files)
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mark Linimon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 04:30 UTC by GNATS administrator
Modified: 2011-02-10 05:33 UTC (History)
0 users

See Also:

Attachments
file.shar (631 bytes, text/plain)
2011-02-10 04:30 UTC, GNATS administrator 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description GNATS administrator freebsd_committer freebsd_triage 2011-02-10 04:30:08 UTC 
Change of maintainer request for the port
www/mod_bandwidth

Change of maintainer for the the port
www/mod_bandwidth

updates for all affected files are attached to this PR

PLEASE NOTE the attached file is in shar(1) format.
But I was forced to rename the file to prevent this web page
from throwing an error.

Fix: Please see attached


Patch attached with submission follows:
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2011-02-10 04:30:15 UTC 
Class Changed
From-To: maintainer-update->change-request

Fix category (submitter is not maintainer) (via the GNATS Auto Assign 
Tool)
Comment 2 Edwin Groothuis freebsd_committer freebsd_triage 2011-02-10 04:30:24 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->apache

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2011-02-10 05:29:05 UTC 
State Changed
From-To: open->closed

Err ... no. 

Let's see if I can provide a quick tutorial on our PR submission 
system :-) 

The idea is not that we have one PR per file changed -- the traffic 
on the mailing list would become overwhelming. 

For new ports (only), we want a sharfile -- of all the files in the 
directory.  (e.g. Makefile, pkg-descr, pkg-plist if there is one, 
distinfo, and anything in files/ .  The work directory should not 
be included). 

For existing ports, we want a single file that is the result of 
diff -ruN against an existing tree.  This allows us to figure out 
what has changed. 

Also, as stated, I'm not sure why you're requesting maintainership of 
a port that already nominally has a maintainer. 

A lot of the above is explained in more detail in: 

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html 
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2011-02-10 05:29:05 UTC 
Responsible Changed
From-To: apache->linimon