From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Felipe Contreras <felipe.contreras@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/3] composing patches
Date: Sat, 11 Dec 2010 00:53:59 +0100 [thread overview]
Message-ID: <87ipz1falk.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <1291933972-7186-1-git-send-email-felipe.contreras@gmail.com>
On Thu, 09 Dec 2010, Felipe Contreras wrote:
> Hi,
>
> I don't know how it works in gnus, but at least on the vim mode, the output
> generated by 'notmuch reply' is not ready to be sent, at least the Message-ID
> field is needed, and also is nice to have the User-Agent.
I'm not sure whether filling the message-id in notmuch is a useful
thing. With Emacs UI I often send messages which differ only in small
pieces to several people. I prepare a first version of the message and
send it, then I edit the sent message and send it once again etc. All of
these messages should have a different message-id and date headers.
If you want to allow the UI to send a single message multiple times (and
I find it useful) then you need generate the message-id at the time of
sending and as such it has no sense to generate the headers in notmuch.
I have nothing against filling User-Agent header as its value does not
change frequently.
-Michal
next prev parent reply other threads:[~2010-12-10 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 22:32 [PATCH 0/3] composing patches Felipe Contreras
2010-12-09 22:32 ` [PATCH 1/3] reply: add message-id header Felipe Contreras
2010-12-09 22:32 ` [PATCH 2/3] reply: add user-agent field Felipe Contreras
2010-12-09 22:32 ` =?no?q?=5BPATCH=203/3=5D=20Add=20=27compose=27=20command?= Felipe Contreras
2010-12-09 23:20 ` [PATCH 0/3] composing patches Sebastian Spaeth
2010-12-10 15:35 ` Felipe Contreras
2010-12-10 16:04 ` Jameson Rollins
2010-12-10 16:38 ` Sebastian Spaeth
2010-12-10 23:53 ` Michal Sojka [this message]
2011-05-04 20:30 ` Felipe Contreras
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipz1falk.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).