From: "(GalaxyMaster)" <galaxy@openwall.com.au>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: backupfile and backup-rename are introducing the same object to make
Date: Sat, 28 Jan 2023 14:41:42 +0000 [thread overview]
Message-ID: <01000185f8d3b73d-eced7384-0372-403f-b259-957314216a10-000000@email.amazonses.com> (raw)
In-Reply-To: <6317250.O3cEFmX14Z@nimes>
Bruno,
On Thu, Jan 26, 2023 at 03:43:01PM +0100, Bruno Haible wrote:
> GalaxyMaster wrote:
> > incremented on interface changes). Despite gnulib's changelog is good in
> > this regard, I am still thinking of finding an automated way to monitor this;
>
> Unfortunately this typically involves developer knowledge about the package.
You've raised a lot of really good questions and I appreciate your insights. I
feel this discussion has already deviated a lot from the original topic and I
am thinking of responding in a different thread. Please be assured that everything
you wrote in the previous message was read and been thought over, however,
responding would produce an even bigger e-mail message and I am not really
ready to type it out right now.
I will try my best to find a way on how to address your questions and still
maintain a message valuable for the rest of the community.
Thanks again for your patience and time!
--
(GM)
prev parent reply other threads:[~2023-01-28 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 12:04 backupfile and backup-replace are introducing the same object to make (GalaxyMaster)
2023-01-25 17:53 ` backupfile and backup-rename " Bruno Haible
2023-01-25 19:44 ` Bruno Haible
2023-01-26 7:28 ` (GalaxyMaster)
2023-01-26 7:19 ` (GalaxyMaster)
2023-01-26 10:19 ` Bruno Haible
2023-01-26 11:20 ` GalaxyMaster
2023-01-26 14:43 ` Bruno Haible
2023-01-28 14:41 ` (GalaxyMaster) [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01000185f8d3b73d-eced7384-0372-403f-b259-957314216a10-000000@email.amazonses.com \
--to=galaxy@openwall.com.au \
--cc=bruno@clisp.org \
--cc=bug-gnulib@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).