gonna be completely honest - i appreciate the patches but i'm not going to go through the labor of applying something this trivial. Unless not using Github is a conscientious protest against ICE or their military contracts or the like , i'm liable to just reject email patches that are not security related or critical fixes on policy grounds.
> On May 28, 2022, at 2:23 PM, Mikolaj Konarski <miko...@well-typed.com> wrote: > > Here you go: > > https://github.com/haskell/cabal/pull/8176 > > If there are review comments, I guess I will be copying them > in emails to you and you will be sending me replies and new > commits to paste into the pull request? > > All the best, > Mikolaj > >> On Sat, May 28, 2022 at 8:55 PM Vilius Panevėžys <v...@mikrovisata.net> >> wrote: >> >> Hi Mikolaj, >> thank you for the prompt reply! >> >> On Sat, 28 May 2022 17:10:24 +0200 >> Mikolaj Konarski <miko...@well-typed.com> wrote: >> >>> Would you like to create a pull request on github with these changes >>> to help us see them in context, e.g., whether they merge cleanly and >>> which branch, and to help us credit you properly? >> >> I don't use GitHub, so I hope it's not too much trouble to just `git >> am` the patches. I've rebased the patches on master today, so they >> should apply cleanly. However, if it turns out you need me to make any >> revision - let me know. >> >> My appreciation goes to all the people who have put in the time and >> effort into creating the user guide (not to mention Cabal itself!). > _______________________________________________ > cabal-devel mailing list > cabal-devel@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
