unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: daniel watson <ozzloy@challenge-bot.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: Fri, 15 Sep 2023 04:47:08 -0700	[thread overview]
Message-ID: <CADwFkmkOx=OaA8Gj97e8riMcYkL7tYjAYS0JALBNZoEVxgh9fg@mail.gmail.com> (raw)
In-Reply-To: <ZQKjw9QkW5lMSX5Z@challenge-bot.com> (daniel watson's message of "Wed, 13 Sep 2023 23:10:11 -0700")

daniel watson <ozzloy@challenge-bot.com> writes:

> i'm including the diff inline to make it easier to review without
> downloading the attached file.

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.





  reply	other threads:[~2023-09-15 11:47 UTC|newest]

Thread overview: 14+ 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 [this message]
2023-09-19  7:15   ` daniel watson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-02 15:02 ` ozzloy
2024-11-05 14:34   ` Sebastián Monía
2024-11-05 17:08     ` Eli Zaretskii
2024-11-05 19:36       ` Jim Porter
2024-11-06  3:30         ` Sebastián Monía
2024-11-06 15:34           ` daniel watson
2024-11-06 23:30         ` Stefan Kangas
2024-11-07  6:20           ` Eli Zaretskii
2024-11-07 18:58             ` Jim Porter
2024-11-08  1:33             ` Stefan Kangas
2024-11-07 18:52         ` Jim Porter

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='CADwFkmkOx=OaA8Gj97e8riMcYkL7tYjAYS0JALBNZoEVxgh9fg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=65973@debbugs.gnu.org \
    --cc=ozzloy@challenge-bot.com \
    --cc=ozzloy@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).