linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: saulery-GANU6spQydw@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/6] intro.1: Add cross references cited
Date: Fri, 06 Mar 2015 14:46:42 +0100	[thread overview]
Message-ID: <54F9AFC2.3070607@gmail.com> (raw)
In-Reply-To: <1425646053-7294-2-git-send-email-saulery-GANU6spQydw@public.gmane.org>

On 03/06/2015 01:47 PM, saulery-GANU6spQydw@public.gmane.org wrote:
> From: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>


Thanks, Stéphane. Applied.

Cheers,

Michael


> Signed-off-by: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
> ---
>  man1/intro.1 | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/man1/intro.1 b/man1/intro.1
> index c554884..0caa0c4 100644
> --- a/man1/intro.1
> +++ b/man1/intro.1
> @@ -300,4 +300,15 @@ and use a browser if you find HTML files there.
>  .\" Actual examples? Separate section for each of cat, cp, ...?
>  .\" gzip, bzip2, tar, rpm
>  .SH SEE ALSO
> +.BR ash (1),
> +.BR bash (1),
> +.BR chsh (1),
> +.BR csh (1),
> +.BR locate (1),
> +.BR login (1),
> +.BR man (1),
> +.BR xterm (1),
> +.BR zsh(1),
> +.BR wait (2),
> +.BR man-pages (7),
>  .BR standards (7)
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-03-06 13:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 12:47 [PATCH 1/6] intro.1: ffix saulery-GANU6spQydw
     [not found] ` <1425646053-7294-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-06 12:47   ` [PATCH 2/6] intro.1: Add cross references cited saulery-GANU6spQydw
     [not found]     ` <1425646053-7294-2-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-06 13:46       ` Michael Kerrisk (man-pages) [this message]
2015-03-06 12:47   ` [PATCH 3/6] intro.1: ffix saulery-GANU6spQydw
     [not found]     ` <1425646053-7294-3-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-06 13:47       ` Michael Kerrisk (man-pages)
2015-03-06 12:47   ` [PATCH 4/6] " saulery-GANU6spQydw
     [not found]     ` <1425646053-7294-4-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-06 13:48       ` Michael Kerrisk (man-pages)
2015-03-06 12:47   ` [PATCH 5/6] " saulery-GANU6spQydw
     [not found]     ` <1425646053-7294-5-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-06 13:48       ` Michael Kerrisk (man-pages)
2015-03-06 12:47   ` [PATCH 6/6] intro.1: Prompt is not % but $ saulery-GANU6spQydw
     [not found]     ` <1425646053-7294-6-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-06 13:48       ` Michael Kerrisk (man-pages)
2015-03-06 13:46   ` [PATCH 1/6] intro.1: ffix Michael Kerrisk (man-pages)

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=54F9AFC2.3070607@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=saulery-GANU6spQydw@public.gmane.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 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).