If the issue is that you aren’t comfortable enough with Git¹, I assume as
part of the basic toolkit of a sysadmin you know how to generate a unified
diff patchfile (with `diff -ruN` or equivalent)?

If so, if you generate one and upload it attached to a GitHub issue, we can
figure out how to turn it into a PR rather trivially (and if I’m the first
to pick it up, I’ll include step-by-step instructions on how to do it as a
Git PR in the future).

—
¹ Though in searching through the email logs to see what familiarity you’d
shown with Git in the past, it seems like this is something that’s held you
back enough that learning it would likely pay large dividends in the future.

On Fri, Jan 17, 2020 at 14:56 Tom Browder <tom.brow...@gmail.com> wrote:

> On Fri, Jan 17, 2020 at 1:44 PM ToddAndMargo via perl6-users
> <perl6-us...@perl.org> wrote:
> ...
> > Was this what you were referring to?
> >
> > https://github.com/Raku/doc/blob/master/CONTRIBUTING.md
>
> No, check this link:
>
>
> https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request
>
> -Tom
>

Reply via email to