From: Jameson Rollins <jrollins@finestructure.net>
To: Carl Worth <cworth@cworth.org>,
Dirk Hohndel <hohndel@infradead.org>,
Sebastian Spaeth <Sebastian@SSpaeth.de>,
Notmuch list <notmuch@notmuchmail.org>
Subject: Re: RFC: User-Agent header
Date: Sat, 10 Apr 2010 09:16:54 -0400 [thread overview]
Message-ID: <87iq7z8n21.fsf@servo.finestructure.net> (raw)
In-Reply-To: <874ojkf23u.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Fri, 09 Apr 2010 19:55:17 -0700, Carl Worth <cworth@cworth.org> wrote:
> So I propose something like:
>
> User-Agent: Notmuch/0.2 (http://notmuchmail.org) Emacs/23.1.1 (gnu/linux)
The problem I see is that if we go with this proposal, our mail will
have inconsistent User-Agent: header, depending on if the message was
new or if it's a reply. Maybe that's not too big of an issue, though,
since the in the reply case notmuch is generating some of the headers,
whereas they're all generated by emacs in the new message case.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2010-04-10 13:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 8:26 RFC: User-Agent header Sebastian Spaeth
2010-04-08 15:12 ` Dirk Hohndel
2010-04-10 2:55 ` Carl Worth
2010-04-10 4:43 ` Dirk Hohndel
2010-04-10 13:16 ` Jameson Rollins [this message]
2010-04-10 14:00 ` Sebastian Spaeth
2010-04-10 14:45 ` Dirk Hohndel
2010-04-10 14:02 ` Xavier Maillard
2010-04-11 22:12 ` Sebastian Spaeth
2010-04-12 5:45 ` David Edmondson
2010-04-12 8:30 ` [PATCH] " Sebastian Spaeth
2010-04-13 17:44 ` Carl Worth
2010-04-13 22:55 ` Xavier Maillard
2010-04-14 7:38 ` [PATCH 13/13] notmuch.el: Add a function to insert a notmuch user-agent header Sebastian Spaeth
2010-04-14 7:44 ` David Edmondson
2010-04-14 9:52 ` Sebastian Spaeth
2010-04-14 7:44 ` [PATCH] RFC: User-Agent header Sebastian Spaeth
2010-04-15 19:52 ` Carl Worth
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=87iq7z8n21.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=Sebastian@SSpaeth.de \
--cc=cworth@cworth.org \
--cc=hohndel@infradead.org \
--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).