Re: Some changes to EPEL package reviews

2011-05-02 Thread Jason L Tibbitts III
GH == Garrett Holmstrom gho...@fedoraproject.org writes: GH How is this any different, given that process-git-requests creates a GH rawhide branch without regard to whether one asks for it or not? I'm catching up with mail after the weekend and noticed this unusually pointed bit of

Re: Some changes to EPEL package reviews

2011-04-29 Thread Kevin Fenzi
On Thu, 28 Apr 2011 22:28:15 -0700 Garrett Holmstrom gho...@fedoraproject.org wrote: On 4/28/2011 13:25, Bill Nottingham wrote: EPEL now has a 'Package Review' component in bugzilla. If you've got an EPEL-only package you'd like to get reviewed, feel free to file it there. How is this

Re: Some changes to EPEL package reviews

2011-04-29 Thread Bill Nottingham
Kevin Fenzi (ke...@scrye.com) said: On 4/28/2011 13:25, Bill Nottingham wrote: EPEL now has a 'Package Review' component in bugzilla. If you've got an EPEL-only package you'd like to get reviewed, feel free to file it there. How is this any different, given that

Re: Some changes to EPEL package reviews

2011-04-29 Thread Jesse Keating
On 4/29/11 8:54 AM, Bill Nottingham wrote: How is this any different, given that process-git-requests creates a rawhide branch without regard to whether one asks for it or not? I think the idea is that it allows people who wish to see reviews that are EPEL only. So, perhaps they

Re: Some changes to EPEL package reviews

2011-04-29 Thread Garrett Holmstrom
On 4/29/2011 9:12, Jesse Keating wrote: It is somewhat difficult, and odd, to create a git repo that does not have a master branch. It would be a little more odd to potentially at some point in the future create the master branch for a package should it find a home within Fedora. As you say,

Re: Some changes to EPEL package reviews

2011-04-28 Thread Garrett Holmstrom
On 4/28/2011 13:25, Bill Nottingham wrote: EPEL now has a 'Package Review' component in bugzilla. If you've got an EPEL-only package you'd like to get reviewed, feel free to file it there. How is this any different, given that process-git-requests creates a rawhide branch without regard to