For this kind of thing the contributor involvement is mostly "mechanical" and (as I imagine) just requires someone going though all PRs, checking if Travis succeeds and the change is really trivial and merging them en masse. This happens from time to time, but using commit access for this if possible is a better thing in my opinion, since it lessens the number of such (obviously boring) work for maintainers.
On 01/20/2015 12:54 AM, Matthias Beyer wrote: > On 20-01-2015 00:46:11, Nikolay Amiantov wrote: >> Nevertheless I want to go though my packages and do version bumps >> in the near future, and I believe this (and things like grammar >> fixes) is kind of patches that should be applied more directly than >> usual, to bother less contributors so that they can focus on >> more non-trivial things. > What keeps you from having a "version-bumping" branch where all your > patches are in and open just one PR for all the patches at once? > -- Nikolay. _______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
