From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Cc: "R. Diez" <rdiezmail-newlib@yahoo.de>
Subject: Re: ChangeLog no longer updated
Date: Wed, 29 Apr 2020 14:15:40 +0200 [thread overview]
Message-ID: <20200429121540.GG4499@calimero.vinschen.de> (raw)
In-Reply-To: <1201185415.4090556.1588161899467@mail.yahoo.com>
On Apr 29 12:04, R. Diez via Newlib wrote:
> Hi all:
>
> The last entry in the ChangeLog file dates from 2016-06-23:
>
> https://sourceware.org/git?p=newlib-cygwin.git;a=blob_plain;f=ChangeLog;hb=HEAD
>
> If this file is no longer maintained, I think it is worth mentioning it in that file itself. For example, the OpenOCD project says the following:
>
> Retired in favor of git log.
>
> It is not ideal, because the Git log is not really designed for users. But at least it tells you what the situation is.
>
> Or is there another place where release information is kept?
Yes:
https://sourceware.org/git/?p=newlib-cygwin.git;a=blob_plain;f=newlib/ChangeLog;hb=HEAD
The top-level ChangeLog is shared between projects and not acticely
maintained by newlib.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
next prev parent reply other threads:[~2020-04-29 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1201185415.4090556.1588161899467.ref@mail.yahoo.com>
2020-04-29 12:04 ` R. Diez
2020-04-29 12:15 ` Corinna Vinschen [this message]
2020-04-29 12:59 ` R. Diez
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200429121540.GG4499@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.org \
--cc=rdiezmail-newlib@yahoo.de \
/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).