From: Andrew Kreimer <algonell@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Documentation: fix typos
Date: Sat, 21 Sep 2024 00:46:34 +0300 [thread overview]
Message-ID: <Zu3tOos7yJnTgbao@void.void> (raw)
In-Reply-To: <xmqq7cb6f5bt.fsf@gitster.g>
On Fri, Sep 20, 2024 at 01:17:10PM -0700, Junio C Hamano wrote:
> Andrew Kreimer <algonell@gmail.com> writes:
>
> > Fix typos in documentation.
> >
> > Signed-off-by: Andrew Kreimer <algonell@gmail.com>
> > ---
>
> Some hunks have become irrelevant between 'master' and 'seen', it
> seems. Please separate them out and resend once these in-flight
> topics are merged to 'master'.
>
> Thanks.
>
On it.
>
> > Documentation/BreakingChanges.txt | 2 +-
> > Documentation/CodingGuidelines | 2 +-
> > Documentation/DecisionMaking.txt | 2 +-
> > Documentation/gitformat-commit-graph.txt | 2 +-
> > Documentation/gitweb.txt | 2 +-
> > 5 files changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt
> > index 2b64665694..112770a9da 100644
> > --- a/Documentation/BreakingChanges.txt
> > +++ b/Documentation/BreakingChanges.txt
> > @@ -117,7 +117,7 @@ Cf. <20140304174806.GA11561@sigill.intra.peff.net>.
> >
> > * The git-pack-redundant(1) command can be used to remove redundant pack files.
> > The subcommand is unusably slow and the reason why nobody reports it as a
> > - performance bug is suspected to be the absense of users. We have nominated
> > + performance bug is suspected to be the absence of users. We have nominated
> > the command for removal and have started to emit a user-visible warning in
> > c3b58472be (pack-redundant: gauge the usage before proposing its removal,
> > 2020-08-25) whenever the command is executed.
> > diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
> > index 3263245b03..8a5e0b7dad 100644
> > --- a/Documentation/CodingGuidelines
> > +++ b/Documentation/CodingGuidelines
> > @@ -838,7 +838,7 @@ Markup:
> > When literal and placeholders are mixed, each markup is applied for
> > each sub-entity. If they are stuck, a special markup, called
> > unconstrained formatting is required.
> > - Unconstrained formating for placeholders is __<like-this>__
> > + Unconstrained formatting for placeholders is __<like-this>__
> > Unconstrained formatting for literal formatting is ++like this++
> > `--jobs` _<n>_
> > ++--sort=++__<key>__
> > diff --git a/Documentation/DecisionMaking.txt b/Documentation/DecisionMaking.txt
> > index dbb4c1f569..b43c472ae5 100644
> > --- a/Documentation/DecisionMaking.txt
> > +++ b/Documentation/DecisionMaking.txt
> > @@ -54,7 +54,7 @@ implementation, for very large changes).
> >
> > For non-technical decisions such as community norms or processes, it is up to
> > the community as a whole to implement and sustain agreed-upon changes.
> > -The project leadership committe (PLC) may help the implementation of
> > +The project leadership committee (PLC) may help the implementation of
> > policy decisions.
> >
> >
> > diff --git a/Documentation/gitformat-commit-graph.txt b/Documentation/gitformat-commit-graph.txt
> > index 3e906e8030..14d1631234 100644
> > --- a/Documentation/gitformat-commit-graph.txt
> > +++ b/Documentation/gitformat-commit-graph.txt
> > @@ -122,7 +122,7 @@ All multi-byte numbers are in network byte order.
> > for commits with corrected commit date offsets that cannot be
> > stored within 31 bits.
> > * Generation Data Overflow chunk is present only when Generation Data
> > - chunk is present and atleast one corrected commit date offset cannot
> > + chunk is present and at least one corrected commit date offset cannot
> > be stored within 31 bits.
> >
> > ==== Extra Edge List (ID: {'E', 'D', 'G', 'E'}) [Optional]
> > diff --git a/Documentation/gitweb.txt b/Documentation/gitweb.txt
> > index 56d24a30a3..5e2b491ec2 100644
> > --- a/Documentation/gitweb.txt
> > +++ b/Documentation/gitweb.txt
> > @@ -234,7 +234,7 @@ from the template during repository creation, usually installed in
> > configuration variable, but the file takes precedence.
> >
> > category (or `gitweb.category`)::
> > - Singe line category of a project, used to group projects if
> > + Single line category of a project, used to group projects if
> > `$projects_list_group_categories` is enabled. By default (file and
> > configuration variable absent), uncategorized projects are put in the
> > `$project_list_default_category` category. You can use the
next prev parent reply other threads:[~2024-09-20 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 8:28 [PATCH 1/3] Documentation/technical: fix a typo Andrew Kreimer
2024-09-20 8:28 ` [PATCH 2/3] Documentation/config: fix typos Andrew Kreimer
2024-09-20 8:28 ` [PATCH 3/3] Documentation: " Andrew Kreimer
2024-09-20 16:55 ` Eric Sunshine
2024-09-20 18:17 ` Junio C Hamano
2024-09-20 20:17 ` Junio C Hamano
2024-09-20 21:46 ` Andrew Kreimer [this message]
2024-09-20 20:12 ` [PATCH 1/3] Documentation/technical: fix a typo Junio C Hamano
2024-09-20 21:42 ` Andrew Kreimer
2024-09-23 17:32 ` Eric Sunshine
2024-09-23 18:55 ` Junio C Hamano
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=Zu3tOos7yJnTgbao@void.void \
--to=algonell@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 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 NNTP newsgroup(s).