From: Olivier Certner <ocert.dev@free.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dmitry@gutov.dev, 62693@debbugs.gnu.org
Subject: bug#62693: 28.2; VC: CVS: Fix lost file reporting and enable reverting it
Date: Mon, 17 Apr 2023 22:10:02 +0200 [thread overview]
Message-ID: <3969694.eEzTlFAC4L@ravel> (raw)
In-Reply-To: <83a5z69z84.fsf@gnu.org>
Hi,
> I should have said "non-trivial". Sorry for potentially confusing
> selection of words.
Non-trivial certainly, but not that complex either (and this thanks to the style used). And, as importantly, this is a component with very delimited and clear functionality and interface, making it simple to reason about from the outside (and this has not been changed by the patch) and see the impacts, especially with a single chain of callers.
> Dmitry asked whether it was okay to install this on the release
> branch, which is currently undergoing pretest. So I looked at the
> changes from the POV of the potential for unintended consequences and
> regressions. This job is much harder when the code is thoroughly
> rewritten, let alone uses a different macro system and style. That is
> why I asked the question: I presume that if the changes were less
> radical, they could perhaps have been deemed appropriate for the
> release branch, or at least the chances for that were higher.
That I can perfectly understand, even if my take would probably be different. That said, I've re-read your mail and it really comes out very differently without such context. So at least thanks for providing it.
> You didn't have to. That's not why I asked the question.
You didn't state the underpinnings, and were apparently adressing to me, not Dmitry, in the rest of the mail, so this is what I inferred for the first paragraph as well. Which then made me lose some time (and subsequently temper), and perhaps made you as well. Proper, transparent communication is key here.
> Not really, but that's a minor point. We can always fix the
> terminology later.
So I guess this means that I'll leave it to you to possibly change names later. Given the previous miscommunication, let me explicitly invite you to manifest yourself if my guess is wrong and you are expecting something else from me on this topic.
Thanks.
--
Olivier Certner
next prev parent reply other threads:[~2023-04-17 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:51 bug#62693: 28.2; VC: CVS: Fix lost file reporting and enable reverting it Olivier Certner
2023-04-12 22:48 ` Dmitry Gutov
2023-04-13 16:40 ` Olivier Certner
2023-04-14 22:59 ` Dmitry Gutov
2023-04-15 9:28 ` Eli Zaretskii
2023-04-17 9:24 ` Olivier Certner
2023-04-17 17:48 ` Eli Zaretskii
2023-04-17 20:10 ` Olivier Certner [this message]
2023-04-19 0:54 ` Dmitry Gutov
2023-04-19 8:10 ` Olivier Certner
2023-04-20 8:55 ` Eli Zaretskii
2023-04-20 9:42 ` Olivier Certner
2023-04-20 10:22 ` Dmitry Gutov
2023-04-17 8:04 ` Olivier Certner
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=3969694.eEzTlFAC4L@ravel \
--to=ocert.dev@free.fr \
--cc=62693@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.