unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] Script to generate ChangeLog-like output
Date: Wed, 16 Jan 2019 10:02:19 -0800	[thread overview]
Message-ID: <f895a31b-bfe7-d0b4-372f-f1d0740897f8@cs.ucla.edu> (raw)
In-Reply-To: <b9077b2f-29eb-99f7-6f93-bd88c4f40488@gotplt.org>

On 1/16/19 9:56 AM, Siddhesh Poyarekar wrote:
> I agree with that idea, but the single script will most likely blow up
> into a set of scripts with the driver and then parsers for backends (c,
> c++, etc.) and quirks (e.g. macros that break the parser) for specific
> projects.  Would that be acceptable?

Sounds good to me.


  reply	other threads:[~2019-01-16 18:02 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
2019-01-16 17:56                 ` Siddhesh Poyarekar
2019-01-16 18:02                   ` Paul Eggert [this message]
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=f895a31b-bfe7-d0b4-372f-f1d0740897f8@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).