all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: philipk@posteo.net, corwin@bru.st, monnier@iro.umontreal.ca,
	info@protesilaos.com, 65027@debbugs.gnu.org
Subject: bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual
Date: Sat, 27 Jan 2024 18:42:00 -0800	[thread overview]
Message-ID: <CADwFkmkefcHBhp-X_ncsiUze2wbdP3B9pyZB=DS6A8MhBHX=Qg@mail.gmail.com> (raw)
In-Reply-To: <c913437a-e14a-9486-7a4d-36181230323f@gmail.com>

Jim Porter <jporterbugs@gmail.com> writes:

> Since no one has had any further comments in the last couple weeks, I've
> now merged my patch to master as 744a10a4d72. Of course, we can work on
> a more elaborate packaging manual in the future. I'll leave this bug
> open for now to discuss that, but if maintainers prefer, we could always
> close this and open a new bug specifically about the packaging manual
> side of things.

Thanks.

I think a new bug is better, indeed:

It takes significant effort to sift through a bug like this one to
uncover that it's not, in fact, about "[PATCH] Document .elpaignore
behavior in the Emacs Lisp manual", but about some other related yet
distinct change.

It's fine to have one or two such bugs, but we have many hundreds.  This
makes using and maintaining the bug tracker harder than it needs to be.





  reply	other threads:[~2024-01-28  2:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  4:56 bug#65027: 30.0.50; [PATCH] Document .elpaignore behavior in the Emacs Lisp manual Jim Porter
2023-08-03  9:02 ` Eli Zaretskii
2023-08-03 13:36   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 17:24     ` Jim Porter
2023-08-03 19:09       ` Philip Kaludercic
2023-08-03 21:21       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 22:02         ` Jim Porter
2023-08-03 22:41           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-04  3:11             ` Jim Porter
2023-09-03 11:18               ` Stefan Kangas
2023-09-06  1:56                 ` Jim Porter
2023-09-06  2:22                   ` Corwin Brust
2023-09-19 13:29                     ` Corwin Brust
2023-09-19 13:53                       ` Protesilaos Stavrou
2023-09-20 10:35                   ` Protesilaos Stavrou
2023-09-21  1:37                     ` Stefan Kangas
2023-08-04  5:42           ` Eli Zaretskii
2023-08-05  1:58       ` Richard Stallman
2023-08-05  2:36         ` Corwin Brust
2023-08-05  6:03           ` Jim Porter
2023-08-05  6:45           ` Eli Zaretskii
2023-08-05 13:17           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-05  6:43         ` Eli Zaretskii
2024-01-10 21:49 ` Stefan Kangas
2024-01-11 19:35   ` Jim Porter
2024-01-27 20:34     ` Jim Porter
2024-01-28  2:42       ` Stefan Kangas [this message]
2024-01-28  5:46       ` Eli Zaretskii
2024-01-28  5:49         ` Stefan Kangas
2024-01-28  7:08           ` Eli Zaretskii
     [not found]   ` <87v8802yrp.fsf@protesilaos.com>
2024-01-11 19:38     ` Stefan Kangas

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='CADwFkmkefcHBhp-X_ncsiUze2wbdP3B9pyZB=DS6A8MhBHX=Qg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=65027@debbugs.gnu.org \
    --cc=corwin@bru.st \
    --cc=info@protesilaos.com \
    --cc=jporterbugs@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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.