public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: rajesh <r.pandian@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Contributing to documentation
Date: Fri, 22 Dec 2023 11:47:25 +0100	[thread overview]
Message-ID: <ZYVpRMcZk2MSg9Yc@debian> (raw)
In-Reply-To: <CAKkEDkU28SRY-dZOVdnGORV2f8ovOak1b=Pr8+bEFDb-B2vx+A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]

[CC += linux-man@]

Hi rajesh,

On Fri, Dec 22, 2023 at 02:27:21PM +0530, rajesh wrote:
> Hi Alejandor,
> 
> Thanks for the help so far. So I think I can contribute to two issues now.

Thanks a lot for helping with the bugzilla bugs!

> However going through the kernel patch videos, I am not sure how to
> apply the patches to man pages.

First of all, you should clone the git repository, and cd(1) into it:

	$ git clone https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
	$ cd man-pages/

I assume you know how to use git, do you?  After cloning that repo,
you'll be able to read the README and CONTRIBUTING files.

Assuming you want to modify mount_namespaces(7), you should edit the
file <./man7/mount_namespaces.7>.

Assuming you know how to use the basics of git(1) to do a commit, then
you can produce a patch with

	$ git format-patch -1 HEAD -o ./patches/ \
	                   --to alx@kernel.org \
	                   --cc linux-man@vger.kernel.org

This will produce a file inside the ./patches/ directory, which you need
to send via email.  You can send it with any mail client to start, and
I can help you refine that.  Most mail clients mess the patch (they
usually mess the whitespace), so it can't be applied with git(1), so you
can configure git-send-email(1) to send it, which will respect the
patch.  mutt(1) or neomutt(1) will by default also respect it, but
git-send-email(1) is probably easier to configure for a start.  Check
this:
<https://git-scm.com/docs/git-send-email#_use_gmail_as_the_smtp_server>


> Attachment is a no no.

What do you mean?  I can accept attachments if you want to send a patch
as an attachment.

> I went through many links but not clear on what's process for patching
> man pages.

Here's the contributing guide we have:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING>

Although you may want to ask for clarification on some things that are
not specified there.

> Can you point me to some link or share some notes please?  I have
> setup git, mutt, and have downloaded the latest stable kernel version.

The Linux man-pages project is different from the Linux kernel project,
and the code is in different repositories.  You don't need the kernel
for contributing to the manual pages.  The guidelines for contributing
are mostly the same, though.

I've CCed the <linux-man@vger.kernel.org> mailing list, to which all
contributions to the project should be sent, as per the contributing
guide I've linked above.

> Kind regards,
> Rajesh

Have a lovely day,
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2023-12-22 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKkEDkWv_wksbcAkUEaFdAQhkhZH1xr+pLidXAvKvV-ka7gE1Q@mail.gmail.com>
     [not found] ` <CAKkEDkU28SRY-dZOVdnGORV2f8ovOak1b=Pr8+bEFDb-B2vx+A@mail.gmail.com>
2023-12-22 10:47   ` Alejandro Colomar [this message]
2023-12-22 14:10     ` Contributing to documentation rajesh
2023-12-22 14:20       ` Alejandro Colomar
2023-12-22 15:08         ` rajesh
2023-12-22 16:47           ` Alejandro Colomar

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=ZYVpRMcZk2MSg9Yc@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=r.pandian@gmail.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