unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: rms@gnu.org
Cc: libc-alpha@sourceware.org, ams@gnu.org, joseph@codesourcery.com,
	carlos@redhat.com
Subject: Re: [PATCH v2] Script to generate ChangeLog-like output
Date: Mon, 14 Jan 2019 20:08:17 +0530	[thread overview]
Message-ID: <ef02976a-1958-d83e-143a-e841ea1a7372@sourceware.org> (raw)
In-Reply-To: <E1ginOf-00011m-Bv@fencepost.gnu.org>

On 14/01/19 3:04 AM, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> Thank you very much for developing this script.
> But we can't presume it works entirely correctly yet.
> Programs tend to have bugs, until we fix them.


Thanks, the plan is to actively maintain the script to add features all 
the way into 2.30 and maybe even 2.31.  The idea of stopping ChangeLog 
writing in 2.29 is to allow us to clean up patchwork and start cleaning 
up our own workflows so that we can automate our patch reviews (or at 
least begin the process) by 2.30 release.  That way by 2.31 we will have 
the automation in place.


It is of course a pie-in-the-sky kind of plan but hopefully we will be 
able to pull it off.  As for the script, I have added it is a project in 
our local makerspace (I get requests from students for projects, 
hopefully this is a simple enough start) and if it is considered 
important enough for GSoC, I don't mind mentoring students working 
globally on additional backends for the script.


Siddhesh


  reply	other threads:[~2019-01-14 14:38 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 [this message]
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
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=ef02976a-1958-d83e-143a-e841ea1a7372@sourceware.org \
    --to=siddhesh@sourceware.org \
    --cc=ams@gnu.org \
    --cc=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=rms@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).