
victor at vsespb
Aug 12, 2013, 1:23 AM
Post #4 of 10
(6 views)
Permalink
|
There is also a page http://perldoc.perl.org/perlrepository.html "SUBMITTING A PATCH VIA GITHUB" And it's hard to tell, when seeing this page, that corresponding perldoc was already removed from Perl repo. It does contain a notice that pull request URL should be emailed, however. perhaps some of PR you see, were emailed? (at least last https://github.com/mirrors/perl/pull/13 was emailed and merged - it was me) 2013/8/12 Ricardo Signes <perl.p5p [at] rjbs> > * Ricardo Signes <perl.p5p [at] rjbs> [2013-08-11T19:10:35] > > I am going to try once more to have the mirror disabled. > > I have sent this message to GitHub support: > > > Hi. I'm the project manager of the perl programming language. > > > > You mirror our repository, providing that mirror at > > https://github.com/mirrors/perl > > > > That's nice. It's fast. > > > > Unfortunately, some users think it is not just a mirror, but the main > > repository, and file pull requests. These pull requests don't come to > the > > development team, and instead get ignored. We miss out on potentially > useful > > bug reports, and the reporters feel stiffed that they're being ignored. > It's > > not good for anyone. > > > > When we last asked about this, in March 2012, we were told it was not > > possible, and that we should add a README. We have one. It's way, way > down > > on the bottom of the page. It isn't useful to discouraging pull > requests. > > > > If we were notified about PRs, that would be one thing… but we still > wouldn't > > be able to close them. At any rate, we don't want more possible avenues > for > > bug reporting. Providing a mechanism for pull requests on read-only > mirrors > > is just a bad idea. > > > > Please let me know if this can be corrected. > > > > Thank you. > > -- > rjbs >
|