aszlig pointed out that we have a pointer in the manual to send patches to the ML if the user in question does not like github which is a valid workflow for me.
BUT we are stagnating in PRs are the moment (390 open PRs) and having a patch per email is overkill. maybe a PR from a different git source instead? i would rather like a git based workflow than having to align the single files into a commit. maybe we have to find a better workflow here which automates things. On 27.06.2017 17:10, Shea Levy wrote: > Mailing list is a perfectly appropriate place to send git patches that > doesn't require membership with a proprietary service; You may not care > about that (I personally don't), but there's no reason we can't > accommodate those who do. > > Joachim Schiele <j...@lastlog.de> writes: > >> please provide your nice patches via a PR on github.com/nixos/nixpkgs to >> 'master' >> >> if you are unsure about the workflow, please ask and we'll help you! >> thanks for your work! >> >> On 25.06.2017 19:51, Karn Kallio wrote: >>> >>> The attached patch fixes the build of the Nixpkgs KDE application >>> okteta by adding some missing dependencies. >>> >>> >>> >>> _______________________________________________ >>> nix-dev mailing list >>> nix-dev@lists.science.uu.nl >>> https://mailman.science.uu.nl/mailman/listinfo/nix-dev >>> >> >> >> _______________________________________________ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> https://mailman.science.uu.nl/mailman/listinfo/nix-dev >> >> >> _______________________________________________ >> nix-dev mailing list >> nix-dev@lists.science.uu.nl >> https://mailman.science.uu.nl/mailman/listinfo/nix-dev _______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev