From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Tomi Ollila <tomi.ollila@iki.fi>,
Mark Walters <markwalters1009@gmail.com>,
Ioan-Adrian Ratiu <adi@adirat.com>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH v2 0/4] Add refresh all buffers functionality
Date: Thu, 06 Oct 2016 09:59:35 -0400 [thread overview]
Message-ID: <87d1jd60jc.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <m2lgygqvt3.fsf@guru.guru-group.fi>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
<silly vocab nitpicking>
On Sun 2016-09-25 03:32:08 -0400, Tomi Ollila wrote:
> 2) then, minor commit message related comment: if there is going to be v3,
> in id:20160924200735.25425-2-adi@adirat.com adi mentioned 'next patches'
> -- those are not patches (anymore) when commits are made, so it would be
> better to reword that sentence. If anythine else doesn't come up, simplest
> thing is to change the word to 'commits'. As said, this is minor thing,
> and we have worse things in commit messages; if there is no need to send
> v3, or the message change is forgotten then it may go in as it is now...
Before these things are accepted into whatever you consider the
canonical git repo to be, while they're still patches floating around in
our various mailboxes, they aren't really "commits" either. I'd use
"changesets" as the generic term.
</silly vocab nitpicking>
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 930 bytes --]
next prev parent reply other threads:[~2016-10-06 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:07 [PATCH v2 0/4] Add refresh all buffers functionality Ioan-Adrian Ratiu
2016-09-24 20:07 ` [PATCH v2 1/4] emacs: reuse buffer when refreshing searches Ioan-Adrian Ratiu
2016-09-25 10:17 ` Mark Walters
2016-09-24 20:07 ` [PATCH v2 2/4] emacs: notmuch-show: refresh all windows showing a buffer Ioan-Adrian Ratiu
2016-09-25 10:14 ` Mark Walters
2016-09-25 12:28 ` Ioan-Adrian Ratiu
2016-09-24 20:07 ` [PATCH v2 3/4] emacs: add refresh buffer optional no-display arg Ioan-Adrian Ratiu
2016-09-25 11:07 ` Mark Walters
2016-10-06 12:25 ` Ioan-Adrian Ratiu
2016-09-24 20:07 ` [PATCH v2 4/4] emacs: notmuch-lib: add refresh all buffers function Ioan-Adrian Ratiu
2016-09-25 11:11 ` Mark Walters
2016-09-24 20:23 ` [PATCH v2 0/4] Add refresh all buffers functionality Ioan-Adrian Ratiu
2016-09-24 21:02 ` Ioan-Adrian Ratiu
2016-09-25 0:09 ` David Bremner
2016-09-25 0:20 ` Ioan-Adrian Ratiu
2016-09-25 6:20 ` Mark Walters
2016-09-25 7:32 ` Tomi Ollila
2016-10-06 13:59 ` Daniel Kahn Gillmor [this message]
2016-10-06 14:32 ` Tomi Ollila
2016-10-06 15:00 ` Ioan-Adrian Ratiu
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=87d1jd60jc.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=adi@adirat.com \
--cc=david@tethera.net \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).