public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216168] updwtmp(3) doesn't mention need for _GNU_SOURCE for updwtmpx
Date: Sun, 03 Jul 2022 18:27:34 +0000	[thread overview]
Message-ID: <bug-216168-11311-3MVIMmtqq9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216168-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216168

Alejandro Colomar (man-pages) (alx.manpages@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |alx.manpages@gmail.com
         Resolution|---                         |DOCUMENTED

--- Comment #3 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
Hi Sam,

Sorry for the delay; I read your posts, but didn't have much time to reply. 
Yes, normally I'd ask for a more detailed commit message, but since it is very
obvious to me that it's correct from this bugzilla report (and also from the
glibc code), and there's a link to this issue in the commit, I think it's OK as
is the patch.

Thanks!

Alex

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2022-07-03 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  2:42 [Bug 216168] New: updwtmp(3) doesn't mention need for _GNU_SOURCE for updwtmpx bugzilla-daemon
2022-06-24  2:45 ` [Bug 216168] " bugzilla-daemon
2022-06-24  5:09 ` bugzilla-daemon
2022-07-03 18:27 ` bugzilla-daemon [this message]

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=bug-216168-11311-3MVIMmtqq9@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@vger.kernel.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