unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jules Tamagnan <jtamagnan@gmail.com>
Cc: 33195-done@debbugs.gnu.org
Subject: bug#33195: 27.0.50; user-login-name has no group-login-name
Date: Sat, 10 Nov 2018 11:24:26 +0200	[thread overview]
Message-ID: <837ehlb7zp.fsf@gnu.org> (raw)
In-Reply-To: <87tvl3cmrj.fsf@gmail.com> (message from Jules Tamagnan on Tue, 30 Oct 2018 11:28:16 -0700)

> From: Jules Tamagnan <jtamagnan@gmail.com>
> Cc: 33195@debbugs.gnu.org
> Date: Tue, 30 Oct 2018 11:28:16 -0700
> 
> I noticed that I had marked GID as optional in the manual, below is a
> patch with that fixed.

Thanks, I pushed this to the master branch, and I'm closing the bug
report.

Please note the following nits for the future:

 . Please include a ChangeLog-style commit log message, which names
   all the new/modified functions and nodes in the manuals.
 . Arguments to functions should be tested for validity, to avoid
   crashes if called with invalid arguments.
 . The first line a of a doc string should be a complete sentence
   shorter than 80 characters, so it fits on a single screen line, and
   it should mention all the mandatory arguments of the function.





      reply	other threads:[~2018-11-10  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 18:52 bug#33195: 27.0.50; user-login-name has no group-login-name Jules Tamagnan
2018-10-30 10:34 ` Eli Zaretskii
2018-10-30 18:25   ` Jules Tamagnan
2018-11-10 18:36     ` Glenn Morris
2018-11-10 18:49       ` Glenn Morris
2018-11-10 19:00         ` Jules Tamagnan
2018-11-10 19:12           ` Glenn Morris
2018-11-10 19:15       ` Eli Zaretskii
2018-11-10 21:02       ` Andreas Schwab
2018-11-11  3:17         ` Glenn Morris
2018-10-30 18:28   ` Jules Tamagnan
2018-11-10  9:24     ` Eli Zaretskii [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837ehlb7zp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33195-done@debbugs.gnu.org \
    --cc=jtamagnan@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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).