From: David Bremner <david@tethera.net>
To: Jesse Rosenthal <jrosenthal@jhu.edu>, notmuch@notmuchmail.org
Subject: Re: [PATCHv2] emacs: derive correct timestamp in FCC unique name
Date: Fri, 22 Jun 2012 07:45:37 -0300 [thread overview]
Message-ID: <87bokbd3qm.fsf@zancas.localnet> (raw)
In-Reply-To: <87y5npg6gc.fsf@jhu.edu>
Jesse Rosenthal <jrosenthal@jhu.edu> writes:
> This change is mostly a question of consistency, since the unique name
> is arbitrary anyway. But since most people use timestamps, and that was
> the original intention here as well, we might as well.
pushed.
d
prev parent reply other threads:[~2012-06-22 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 20:01 [PATCH] emacs: derive correct timestamp in FCC unique name Jesse Rosenthal
2012-06-14 9:43 ` Tomi Ollila
2012-06-14 16:35 ` Jesse Rosenthal
2012-06-14 17:16 ` [PATCHv2] " Jesse Rosenthal
2012-06-14 19:04 ` Tomi Ollila
2012-06-22 10:45 ` David Bremner [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bokbd3qm.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=jrosenthal@jhu.edu \
--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).