linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/3] resolv.conf.5: document RES_SNGLKUPREOP
Date: Wed, 22 Apr 2015 12:03:36 +0200	[thread overview]
Message-ID: <20150422100336.GA25430@free.fr> (raw)
In-Reply-To: <55377257.3010804-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Le mercredi 22 avril 2015 à 12:05:11, Michael Kerrisk (man-pages) a écrit :
> On 04/22/2015 11:10 AM, Stéphane Aulery wrote:
> > 
> > Le mercredi 22 avril 2015 à 11:11:30, Michael Kerrisk (man-pages) a écrit :
> >> On 04/22/2015 02:21 AM, saulery-GANU6spQydw@public.gmane.org wrote:
> >>> From: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
> >>>
> >>> Fix Ubuntu bug #1110781:
> >>> https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1110781
> >>
> >> I need some help here. How is this patch fixing that bug.
> >> I need a short explanation of the connection for the changelog.
> > 
> > Yes, this bug have been partially resolved by commit:
> > 
> > https://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man5/resolv.conf.5?id=aa87a3f3f8c74fc1f5cb614f6e63aea34fe1a459
> > 
> > and tagged fixe-upstream by Simon Paillard for this Debian bug #699387.
> > 
> > Ubuntu bug #1110781 report is more comprehensive and passing I saw that
> > RES_SNGLKUPREOP was missed.
> 
> Thanks, patch applied. And I added the above points to the changelog.

Ok, thanks.

-- 
Stéphane Aulery
--
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-04-22 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  0:21 [PATCH 1/3] resolv.conf.5: document use-vc option added to glibc 2.14 saulery-GANU6spQydw
     [not found] ` <1429662071-23797-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-04-22  0:21   ` [PATCH 2/3] resolv.conf.5: ffix saulery-GANU6spQydw
     [not found]     ` <1429662071-23797-2-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-04-22  9:09       ` Michael Kerrisk (man-pages)
2015-04-22  0:21   ` [PATCH 3/3] resolv.conf.5: document RES_SNGLKUPREOP saulery-GANU6spQydw
     [not found]     ` <1429662071-23797-3-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-04-22  9:11       ` Michael Kerrisk (man-pages)
     [not found]         ` <553765C2.6060807-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-22  9:10           ` Stéphane Aulery
     [not found]             ` <20150422091013.GA4051-GANU6spQydw@public.gmane.org>
2015-04-22 10:05               ` Michael Kerrisk (man-pages)
     [not found]                 ` <55377257.3010804-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-22 10:03                   ` Stéphane Aulery [this message]
2015-04-22  9:08   ` [PATCH 1/3] resolv.conf.5: document use-vc option added to glibc 2.14 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=20150422100336.GA25430@free.fr \
    --to=saulery-ganu6spqydw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).