bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Bruno Haible <bruno@clisp.org>
Cc: "bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: Re: mountlist: Merge two .m4 files
Date: Sat, 26 Jan 2019 21:11:12 -0800	[thread overview]
Message-ID: <CA+8g5KGLnC8Ckjr4cSciMjeWzJxhpfiHTf2pphjom+m_UY5=kQ@mail.gmail.com> (raw)
In-Reply-To: <7076910.ARmdMDCjrg@omega>

On Sat, Jan 26, 2019 at 3:45 PM Bruno Haible <bruno@clisp.org> wrote:
> It is strange (and hampers maintenance) that the main macros for module
> 'mountlist' are not found in mountlist.m4 but in a file with a hard-to-remember
> name 'ls-mntd-fs.m4'.
>
> I propose to merge ls-mntd-fs.m4 into mountlist.m4, to align it with the
> common practices of most other gnulib modules.
>
> Surely no one uses ls-mntd-fs.m4 independently of gnulib, nowadays.
>
>
> 2019-01-26  Bruno Haible  <bruno@clisp.org>
>
>         mountlist: Merge two .m4 files.
>         * m4/mountlist.m4 (gl_MOUNTLIST): Inline gl_LIST_MOUNTED_FILE_SYSTEMS.
>         (AC_FUNC_GETMNTENT): Move to here, from m4/ls-mntd-fs.m4.
>         * m4/ls-mntd-fs.m4: Remove file.
>         * modules/mountlist (Files): Remove m4/ls-mntd-fs.m4.

Hi Bruno,
You're welcome to merge those. Thanks for all of your work tending gnulib.


  reply	other threads:[~2019-01-27  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 23:44 mountlist: Merge two .m4 files Bruno Haible
2019-01-27  5:11 ` Jim Meyering [this message]
2019-01-27 10:46   ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to='CA+8g5KGLnC8Ckjr4cSciMjeWzJxhpfiHTf2pphjom+m_UY5=kQ@mail.gmail.com' \
    --to=jim@meyering.net \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).