unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: me@eshelyaron.com, 65387@debbugs.gnu.org
Subject: bug#65387: [PATCH] New user option 'submit-emacs-patch-display-help'
Date: Wed, 06 Sep 2023 21:31:35 +0300	[thread overview]
Message-ID: <83cyyv17co.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkRWMmEBwtk0SCoJEvR6=oOS9fXmD9vgOv2H-xP+0=kqA@mail.gmail.com> (message from Stefan Kangas on Wed, 6 Sep 2023 10:47:41 -0700)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 6 Sep 2023 10:47:41 -0700
> Cc: Eshel Yaron <me@eshelyaron.com>, 65387@debbugs.gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Would people please voice their opinions about adding it?
> 
> I think it would be nice to eventually make `M-x submit-emacs-patch'
> into something even more powerful, more suitable for advanced users.
> 
> I'm thinking of something closer to debbugs, so that you set some option
> to your Emacs source tree, and it'll create the patches and attach them
> to the current email for you.
> 
> So I think I like the idea here, as it seems to go in that direction.

TBH, I fail to see how disabling the instruction is going in the
direction you described.  But if this is part of some larger plan to
that effect, I don't mind.





      reply	other threads:[~2023-09-06 18:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19 19:33 bug#65387: [PATCH] New user option 'submit-emacs-patch-display-help' Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 19:58 ` Eli Zaretskii
2023-08-19 20:56   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20  6:07     ` Eli Zaretskii
2023-08-20  7:56       ` Visuwesh
2023-08-20  9:59       ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 11:35         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 16:37       ` Juri Linkov
2023-11-16  7:25         ` Juri Linkov
2023-12-15  1:12           ` Stefan Kangas
2023-09-06 17:47       ` Stefan Kangas
2023-09-06 18:31         ` Eli Zaretskii [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=83cyyv17co.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65387@debbugs.gnu.org \
    --cc=me@eshelyaron.com \
    --cc=stefankangas@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 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).