Re: Found error in documentation, looking for advice on how to start contributing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Dominik,

Welcome to the list.

On Fri, 5 Mar 2021 at 02:04, Dominik Lameter <dominik@xxxxxxxxxx> wrote:
> I don't know if this is the place for this question, let me know if I
> should send it elsewhere.
>
> this would be a simple place to start. I've read through the readme
> and Documentation/SubmittingPatches document, however with the
> https://github.com/git/git repository being publish only, what git
> repository do I base my changes on for documentation patches?

You can certainly clone from github.com/git/git, no problem, or make a
fork. The "publish only" remark means that commits/patches don't reach
that repo through pull requests, i.e., they don't really enter "through"
GitHub. Rather, they reach Junio (the maintainer) through this mailing
list. He'll carefully collect the various topics flying around here and
turn them into branches, and publish those at various places, one of
which is github.com. Thus "publish only". Anyway, long story short,
you've found the right place. :-)

And all that said, there is a way of making a GitHub pull request in a
way that it reaches this mailing list: GitGitGadget. I saw that Emily
referred you to MyFirstContribution.txt -- you'll find more there.

By the time you feel ready to submit a patch, feel free to cc me and
I'd be happy to try to review it. And even before then, if you have any
questions, just ask. :-)

Martin



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux