From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: newlib@sourceware.org
Subject: Re: ChangeLog no longer updated
Date: Wed, 29 Apr 2020 14:59:05 +0200 [thread overview]
Message-ID: <69bb224f-b156-7807-d3a2-5abc3a4ed3cb@yahoo.de> (raw)
In-Reply-To: <20200429121540.GG4499@calimero.vinschen.de>
> 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.
Thanks for the quick answer.
Is there any other project using the top-level Changelog? Because it does not look that way. I would then add to the top of that file a comment about
where to find the ChangeLog for each separate project. Or just some generic statement like "Each project maintains its separate ChangeLog, check the
project's subdirectory".
The reason behind this nitpicking is that I am often frustrated by Newlib's documentation. It's like death by a thousand cuts, you waste a little
everywhere. I just wish you could find information more naturally.
Best regards,
rdiez
prev parent reply other threads:[~2020-04-29 12:59 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
2020-04-29 12:59 ` R. Diez [this message]
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=69bb224f-b156-7807-d3a2-5abc3a4ed3cb@yahoo.de \
--to=rdiezmail-newlib@yahoo.de \
--cc=newlib@sourceware.org \
--cc=vinschen@redhat.com \
/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).