From: Phillip Wood <phillip.wood123@gmail.com>
To: Dragan Simic <dsimic@manjaro.org>, Hans Meiser <brille1@hotmail.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
git@vger.kernel.org
Subject: Re: Migrate away from vger to GitHub or (on-premise) GitLab?
Date: Fri, 2 Feb 2024 11:07:18 +0000 [thread overview]
Message-ID: <6b34d999-3da2-42ef-bfff-37c8f592347f@gmail.com> (raw)
In-Reply-To: <691395bc13ea6c3013adcb98cfcbd102@manjaro.org>
On 01/02/2024 19:00, Dragan Simic wrote:
> On 2024-02-01 19:36, Hans Meiser wrote:
> Please keep in mind that editing the git man pages requires very
> intimate knowledge of the related git source code. Many times even
> small changes to the language style can change the meaning and diverge
> the man pages from the source code, making the man pages useless.
While there are some aspects of the documentation that require a
familiarity with the source I don't think that is true in general. If
someone has a suggestion to improve part of the documentation that they
found hard to understand we should be encouraging them to contribute a
patch. There is no doubt that there are places where our documentation
could be improved and it is not necessary to be a C programmer to
contribute improvements to it.
Best Wishes
Phillip
next prev parent reply other threads:[~2024-02-02 11:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AS2P195MB21350F44B079009C05A1EAF1E2432@AS2P195MB2135.EURP195.PROD.OUTLOOK.COM>
2024-02-01 12:10 ` Migrate away from vger to GitHub or (on-premise) GitLab? Hans Meiser
2024-02-01 12:20 ` Antonin Delpeuch
2024-02-01 12:21 ` Kristoffer Haugsbakk
2024-02-01 17:39 ` Hans Meiser
2024-02-01 12:56 ` Dragan Simic
2024-02-01 15:39 ` Konstantin Ryabitsev
2024-02-01 16:54 ` Dragan Simic
2024-02-01 17:00 ` Dragan Simic
2024-02-01 17:28 ` Hans Meiser
2024-02-01 17:49 ` Dragan Simic
2024-02-01 18:36 ` Hans Meiser
2024-02-01 19:00 ` Dragan Simic
2024-02-01 20:01 ` rsbecker
2024-02-01 20:09 ` Dragan Simic
2024-02-02 10:21 ` Hans Meiser
2024-02-02 10:18 ` Hans Meiser
2024-02-02 10:54 ` Dragan Simic
2024-02-02 11:23 ` Muting and unmuting threads (Was: Migrate away from vger to GitHub or (on-premise) GitLab?) Dragan Simic
2024-02-02 11:07 ` Phillip Wood [this message]
2024-02-02 11:13 ` Migrate away from vger to GitHub or (on-premise) GitLab? Dragan Simic
2024-02-02 19:02 ` Junio C Hamano
2024-02-02 1:44 ` brian m. carlson
2024-02-02 5:10 ` Patrick Steinhardt
2024-02-02 11:15 ` Phillip Wood
2024-02-02 11:50 ` Michal Suchánek
2024-02-02 12:36 ` Dragan Simic
2024-02-04 15:12 ` Oswald Buddenhagen
2024-02-04 15:28 ` Dragan Simic
2024-02-04 15:51 ` Michal Suchánek
2024-02-04 15:58 ` Dragan Simic
2024-02-04 15:47 ` Michal Suchánek
2024-02-05 1:04 ` Oswald Buddenhagen
2024-02-02 10:43 ` Hans Meiser
2024-02-02 10:48 ` Hans Meiser
2024-02-01 17:46 ` Nico Williams
2024-02-01 17:39 ` Kristoffer Haugsbakk
2024-02-02 14:49 ` Sergey Organov
2024-02-02 15:22 ` rsbecker
2024-02-02 16:16 ` Theodore Ts'o
2024-02-02 17:23 ` Michal Suchánek
2024-02-02 19:04 ` Junio C Hamano
2024-02-02 21:28 ` Theodore Ts'o
2024-02-06 7:22 ` Hans Meiser
2024-02-06 8:06 ` Dragan Simic
2024-02-02 16:41 ` Junio C Hamano
2024-02-02 17:06 ` rsbecker
2024-02-02 17:39 ` Junio C Hamano
2024-02-02 17:50 ` rsbecker
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=6b34d999-3da2-42ef-bfff-37c8f592347f@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=brille1@hotmail.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=phillip.wood@dunelm.org.uk \
/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).