unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] Script to generate ChangeLog-like output
Date: Wed, 16 Jan 2019 09:44:37 -0800	[thread overview]
Message-ID: <61f2bc4d-4fdf-5d60-a8e9-01dccfb6c578@cs.ucla.edu> (raw)
In-Reply-To: <alpine.DEB.2.21.1901161722560.16346@digraph.polyomino.org.uk>

On 1/16/19 9:29 AM, Joseph Myers wrote:
> Note that the scripts do different things.  The gnulib script is for the
> case where the commit messages include ChangeLog-like content.  The glibc
> one is for the case where the commit messages do not try to list changed
> entities or what changed in those entities, but where an
> automatically-generated list of changed entities is considered good enough

Yes, the idea is that Emacs, coreutils, etc. will switch to the Glibc 
approach. Nobody prefers the current Gnulib approach, as far as I know; 
it's used only because the Gnulib script was easier to write.


  reply	other threads:[~2019-01-16 17:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12 11:24 [PATCH v2] Script to generate ChangeLog-like output Siddhesh Poyarekar
2019-01-13 21:34 ` Richard Stallman
2019-01-14 14:38   ` Siddhesh Poyarekar
2019-01-14 14:43     ` Siddhesh Poyarekar
2019-01-15 21:36       ` Richard Stallman
2019-01-16  3:35         ` Siddhesh Poyarekar
2019-01-16  5:27           ` Rical Jasan
2019-01-16 15:28             ` Siddhesh Poyarekar
2019-01-16 15:47               ` Siddhesh Poyarekar
2019-01-16 16:54           ` Alfred M. Szmidt
2019-01-16 16:59             ` Siddhesh Poyarekar
2019-01-16 17:21               ` Paul Eggert
2019-01-16 17:29                 ` Joseph Myers
2019-01-16 17:44                   ` Paul Eggert [this message]
2019-01-16 17:56                 ` Siddhesh Poyarekar
2019-01-16 18:02                   ` Paul Eggert
2019-01-15 21:36     ` Richard Stallman

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/libc/involved.html

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

  git send-email \
    --in-reply-to=61f2bc4d-4fdf-5d60-a8e9-01dccfb6c578@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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).