git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <sbeller@google.com>
To: "René Genz" <liebundartig@freenet.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: minor typos in documentation
Date: Wed, 19 Apr 2017 13:55:11 -0700	[thread overview]
Message-ID: <CAGZ79kavV-58JyUce9BMO9S3LVKGeUBQU-Qt79LAR41xgr=MxA@mail.gmail.com> (raw)
In-Reply-To: <ea2780fd-8d63-6060-fb17-df5720bbc3de@freenet.de>

On Wed, Apr 19, 2017 at 1:44 PM, René Genz <liebundartig@freenet.de> wrote:
> Dear sir or madam,
>
> At:
> https://git-scm.com/docs/git-commit#git-commit---long
>
> you can read:
> When doing a dry-run, give the output in a the long-format.
>
> From my point of view it should read:
> When doing a dry-run, give the output in the long-format.
>
>
>
> Furthermore in the file:
> ./Documentation/gitremote-helpers.txt
>
> you can read:
> As the a push option
>
> It should be changed to:
> As the push option
>
>
>
> Additionally in the file:
> ./ci/run-windows-build.sh
>
> please change:
> # Script to trigger the a Git for Windows build and test run.
>
> to:
> # Script to trigger the Git for Windows build and test run.
>
>
>
> And in the file:
> ./diff.c
>
> change:
>  *   1. collect a the minus/plus lines of a diff hunk, divided into
>
> to:
>  *   1. collect the minus/plus lines of a diff hunk, divided into
>
> Thanks a lot in advance for fixing these minor typos.

Thanks for spotting the errors!

Care to craft a patch and send it upstream yourself?
See https://github.com/git/git/blob/master/Documentation/SubmittingPatches
how to approach it.
TL;DR:
    git clone https://github.com/git/git
    # hack hack hack
    git commit
    git format-patch HEAD^
    # use e.g. git send-email to send the patch to the mailing list

Thanks,
Stefan

  reply	other threads:[~2017-04-19 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 20:44 minor typos in documentation René Genz
2017-04-19 20:55 ` Stefan Beller [this message]
2017-04-19 23:54   ` René Genz
2017-04-23 16:22     ` René Genz
2017-04-24 16:02       ` Stefan Beller

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='CAGZ79kavV-58JyUce9BMO9S3LVKGeUBQU-Qt79LAR41xgr=MxA@mail.gmail.com' \
    --to=sbeller@google.com \
    --cc=git@vger.kernel.org \
    --cc=liebundartig@freenet.de \
    /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).