From: daniel watson via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 65973@debbugs.gnu.org, daniel watson <ozzloy@gmail.com>
Subject: bug#65973: [PATCH] ; send filename, not full path, on EWW form submit
Date: Tue, 19 Sep 2023 00:15:45 -0700 [thread overview]
Message-ID: <ZQlKoWNaCuDCRAZ2@challenge-bot.com> (raw)
In-Reply-To: <CADwFkmkOx=OaA8Gj97e8riMcYkL7tYjAYS0JALBNZoEVxgh9fg@mail.gmail.com>
On Fri, Sep 15, 2023 at 04:47:08AM -0700, Stefan Kangas wrote:
> Most (or all?) people reviewing patches use Emacs mail readers, so we
> have no trouble reviewing attached files. Getting it as an attachment
> actually makes things easier for us, as our tools are adapted to that
> workflow. That's the main reason why we have a preference for that
> format.
that makes sense. i want to get my email setup like that.
the inline patch was included for easier viewing in the browser and not
as a replacement for the attachment, or endorsing skipping the
attachment. so i'm glad you clarified
on the last bug report, when i got help from people, i found myself
linking to both the bug report page, and separately to another page
where they could view the code in-browser. maybe the bug report page
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65973
could display the attached patch in addition to having a download link.
the source code for this page has not been touched in years though, so
that makes me think it will be difficult to contribute a change.
thanks for the assistance with this and the prior bug!
next prev parent reply other threads:[~2023-09-19 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 6:10 bug#65973: [PATCH] ; send filename, not full path, on EWW form submit daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-15 11:47 ` Stefan Kangas
2023-09-19 7:15 ` daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-02 15:02 ` ozzloy
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=ZQlKoWNaCuDCRAZ2@challenge-bot.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65973@debbugs.gnu.org \
--cc=ozzloy@each.do \
--cc=ozzloy@gmail.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 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.