From: Eli Zaretskii <eliz@gnu.org>
To: Sergey Vinokurov <serg.foo@gmail.com>
Cc: p.stephani2@gmail.com, dancol@dancol.org, 69953@debbugs.gnu.org
Subject: bug#69953: [PATCH] Remove duplicated asserts and checks
Date: Sat, 11 May 2024 16:05:15 +0300 [thread overview]
Message-ID: <86v83k1otw.fsf@gnu.org> (raw)
In-Reply-To: <744fc21b-8a32-4bdc-bd58-08e1066ca20e@gmail.com> (message from Sergey Vinokurov on Sat, 11 May 2024 13:57:31 +0100)
> Date: Sat, 11 May 2024 13:57:31 +0100
> Cc: p.stephani2@gmail.com, dancol@dancol.org, 69953@debbugs.gnu.org
> From: Sergey Vinokurov <serg.foo@gmail.com>
>
> It's small indeed and maybe even inconsequential. But as the saying
> goes, the devil is in the details - the small things. Another reason to
> bother is to see whether I can manage to get small things merged -
> bigger contributions would likely involve all the hard parts of merging
> small contributions and then some. If I'm not able to finish small
> things then bigger ones are unlikely to succeed.
I'm sure you will find a lot of other opportunities for small
contributions, no need to extrapolate from this one.
In many places in Emacs, there's more to the code than meets the eye,
so bitter experience taught me to be extremely cautious with code I'm
not familiar enough.
next prev parent reply other threads:[~2024-05-11 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 3:27 bug#69953: [PATCH] Remove duplicated asserts and checks Sergey Vinokurov
2024-03-23 7:15 ` Eli Zaretskii
2024-03-23 12:38 ` Sergey Vinokurov
2024-04-13 7:42 ` Eli Zaretskii
2024-04-27 8:27 ` Eli Zaretskii
2024-05-09 7:24 ` Eli Zaretskii
2024-05-09 14:16 ` Sergey Vinokurov
2024-05-11 10:02 ` Eli Zaretskii
2024-05-11 12:12 ` Sergey Vinokurov
2024-05-11 12:18 ` Eli Zaretskii
2024-05-11 12:57 ` Sergey Vinokurov
2024-05-11 13:05 ` Eli Zaretskii [this message]
2024-05-11 13:11 ` Daniel Colascione
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=86v83k1otw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69953@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=p.stephani2@gmail.com \
--cc=serg.foo@gmail.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.
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.