git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: Dominik Lameter <dominik@graphe.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Found error in documentation, looking for advice on how to start contributing
Date: Fri, 5 Mar 2021 18:08:00 +0100	[thread overview]
Message-ID: <CAN0heSoE2-xPaAZSB5A12=QDOPZpsGoR-FqmFKuc7OC79wH=FQ@mail.gmail.com> (raw)
In-Reply-To: <CAPhpCMJ-u+W5+6ckazo7JkeaPhkpGP_6hOSJcggor0CcYgU95Q@mail.gmail.com>

Hi Dominik,

Welcome to the list.

On Fri, 5 Mar 2021 at 02:04, Dominik Lameter <dominik@graphe.net> 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

      parent reply	other threads:[~2021-03-05 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  0:04 Found error in documentation, looking for advice on how to start contributing Dominik Lameter
2021-03-05  0:31 ` Emily Shaffer
2021-03-05  1:38   ` Dominik Lameter
2021-03-05 17:08 ` Martin Ågren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN0heSoE2-xPaAZSB5A12=QDOPZpsGoR-FqmFKuc7OC79wH=FQ@mail.gmail.com' \
    --to=martin.agren@gmail.com \
    --cc=dominik@graphe.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).