unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Burks <rburksdev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70182@debbugs.gnu.org
Subject: bug#70182: [PATCH] Fix + ert for segmentation fault in get-variable-watchers (1 of 9)
Date: Sun, 7 Apr 2024 13:43:45 -0400	[thread overview]
Message-ID: <CAHvcHq6g-81sRb4xBLg+rEgrqXT4sgO5s-FwzVSRZwVaqWYU6g@mail.gmail.com> (raw)
In-Reply-To: <86bk6l1u5z.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

Got it.

On Sun, Apr 7, 2024 at 3:58 AM Eli Zaretskii <eliz@gnu.org> wrote:

> [Please use Reply All to reply, to keep the bug tracker CC'ed.]
>
> > From: Robert Burks <rburksdev@gmail.com>
> > Date: Sun, 7 Apr 2024 02:30:54 -0400
> >
> > I will make the changes.  Sorry if my previous reply came across as
> rash, wasn't the intent.
> > Should I remove the bug number tag also?
>
> The bug number should be mentioned in the commit log message, not in
> the sources.
>
> > Also, kicking myself, I know they should end with a period and two
> spaces, every other
> > comment I've written probably does.  Somehow the only ones I didn't
> check was the very
> > first patch, lol.  That first comment wasn't even supposed to go out,
> that was my personal note
> > for when I was going through looking for more of the same bug.
> >
> > There will probably be other comments to remove.
>
> Thanks.
>

[-- Attachment #2: Type: text/html, Size: 1409 bytes --]

      reply	other threads:[~2024-04-07 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  8:44 bug#70182: [PATCH] Fix + ert for segmentation fault in get-variable-watchers (1 of 9) Robert Burks
2024-04-06  7:25 ` Eli Zaretskii
     [not found]   ` <CAHvcHq7CHrWSV8PkSmfWx_RwETK9OOwm4eJqH6wTZtifA-FEtw@mail.gmail.com>
2024-04-07  7:58     ` Eli Zaretskii
2024-04-07 17:43       ` Robert Burks [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=CAHvcHq6g-81sRb4xBLg+rEgrqXT4sgO5s-FwzVSRZwVaqWYU6g@mail.gmail.com \
    --to=rburksdev@gmail.com \
    --cc=70182@debbugs.gnu.org \
    --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 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).