From: Stefan Kangas <stefankangas@gmail.com>
To: "Daniel Martín" <mardani29@yahoo.es>, 61441@debbugs.gnu.org
Subject: bug#61441: Fix typo in buffer.h
Date: Sun, 12 Feb 2023 02:51:37 +0000 [thread overview]
Message-ID: <CADwFkm=8Sob=9b6br6nFoetLUJTrBv2Ri7P6Hf+L-PEtj2DMqw@mail.gmail.com> (raw)
In-Reply-To: <m14jrroh5i.fsf@yahoo.es>
close 61441 29.1
thanks
Daniel Martín writes:
> I've attached a patch to fix a small typo in a comment in buffer.h.
Thanks, pushed to emacs-29 (commit 8f3091defb3).
prev parent reply other threads:[~2023-02-12 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m14jrroh5i.fsf.ref@yahoo.es>
2023-02-12 0:34 ` bug#61441: Fix typo in buffer.h Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 2:51 ` Stefan Kangas [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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=8Sob=9b6br6nFoetLUJTrBv2Ri7P6Hf+L-PEtj2DMqw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=61441@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).