[Nix-dev] okteta fix build

[Alexandre Peyroux]

Certainly but on big projects that have many developers and a lot of PR, it
loses its charm.

Le mar. 27 juin 2017 à 19:44, Linus Heckemann <acc at sphalerite.org> a écrit :

> On 27/06/17 17:01, Joachim Schiele wrote:
> > 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.
>
> FWIW this *is* a git-based workflow, git comes with the ability to
> format patches for emails and import such patches (and was designed with
> this in mind for use in the development of linux) — see man
> git-format-patch and git-am. I personally think it's fine receiving
> patches like this — if volume increases maybe there should be another
> list specifically for patches, but at current levels IMHO it's no problem.
>
> Linus
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> https://mailman.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.science.uu.nl/pipermail/nix-dev/attachments/20170627/1c264401/attachment.html>