all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 62320@debbugs.gnu.org
Subject: bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs")
Date: Thu, 23 Mar 2023 15:34:40 +0200	[thread overview]
Message-ID: <83wn374mmn.fsf@gnu.org> (raw)
In-Reply-To: <87bkklcypz.fsf@web.de> (message from Michael Heerdegen on Wed, 22 Mar 2023 03:21:44 +0100)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 62320@debbugs.gnu.org
> Date: Wed, 22 Mar 2023 03:21:44 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > > The first I want to say is that, while we are telling a lot of
> > > (technical) details, we are missing a bit to tell what creating a bug
> > > report means practically, how it works in general.  I mean simple things
> > > like these that are trivial for us but still not clear to everybody:
> >
> > "Bugs" is a catch-all chapter with almost no contents of its own; all
> > the real contents is in its sections.  Are your comments to that
> > chapter, or specifically to one of its sections, such as "Checklist"?
> > It is hard to think about your comments without understanding to which
> > part(s) of the manual are they alluding.
> 
> I'm just missing this kind of information in general.  This was not
> intended as a comment to a specific chapter.
> 
> But I think this would fit best (and maybe only) into
> (info "(emacs) Checklist") indeed.
> 
> Maybe we could just insert a short summary text like mine as new third
> paragraph?

I've made some changes in that section, please take a look.





  reply	other threads:[~2023-03-23 13:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  5:23 bug#62320: 30.0.50; Thoughts about (info "(emacs) Bugs") Michael Heerdegen
2023-03-21 14:21 ` Eli Zaretskii
2023-03-22  2:21   ` Michael Heerdegen
2023-03-23 13:34     ` Eli Zaretskii [this message]
2023-03-29 15:19       ` Michael Heerdegen
2023-03-29 15:52         ` Eli Zaretskii
2023-03-30 16:08           ` Michael Heerdegen
2023-04-01 10:02             ` Eli Zaretskii
2023-07-20  2:26               ` Michael Heerdegen
2023-07-20  5:02                 ` Eli Zaretskii
2023-07-21  2:42                 ` Richard Stallman
2023-07-21  5:53                   ` Eli Zaretskii
2023-07-23  3:01                     ` Richard Stallman
2023-07-21  7:55                   ` Michael Albinus
2023-07-23  3:01                     ` Richard Stallman

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=83wn374mmn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62320@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.