From: Emily Shaffer <emilyshaffer@google.com>
To: Dominik Lameter <dominik@graphe.net>
Cc: git@vger.kernel.org, git-mentoring@googlegroups.com
Subject: Re: Found error in documentation, looking for advice on how to start contributing
Date: Thu, 4 Mar 2021 16:31:11 -0800 [thread overview]
Message-ID: <YEF7z38st+4pEvdA@google.com> (raw)
In-Reply-To: <CAPhpCMJ-u+W5+6ckazo7JkeaPhkpGP_6hOSJcggor0CcYgU95Q@mail.gmail.com>
On Thu, Mar 04, 2021 at 06:04:01PM -0600, Dominik Lameter wrote:
>
> Hi all,
Hi and welcome!
>
> I don't know if this is the place for this question, let me know if I
> should send it elsewhere.
>
> I was reading a portion of the documentation today and found a
> paragraph out of place in my local documentation, as well as on
> https://git-scm.com/docs/git-log and in the git/git GitHub repository.
> I have never contributed to an open source project before and I think
> 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?
I think the My First Contribution guide can help you, especially if you
start from here:
https://git-scm.com/docs/MyFirstContribution#add-documentation
(The rest of the guide before that anchor may also be useful to you, but
not specifically for a documentation change.)
This is definitely the right list, so do write back if you have
questions that aren't answered by that guide.
- Emily
next prev parent reply other threads:[~2021-03-05 0:31 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 [this message]
2021-03-05 1:38 ` Dominik Lameter
2021-03-05 17:08 ` Martin Ågren
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEF7z38st+4pEvdA@google.com \
--to=emilyshaffer@google.com \
--cc=dominik@graphe.net \
--cc=git-mentoring@googlegroups.com \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.