From: "W. Trevor King" <wking@tremily.us>
To: notmuch@notmuchmail.org
Subject: [PATCH 0/2] nmbug: Bump to 0.3 and document in NEWS
Date: Thu, 28 Dec 2017 10:11:56 -0800 [thread overview]
Message-ID: <cover.1514484376.git.wking@tremily.us> (raw)
As discussed previously in [1,2,3]. I've split this into two patches,
and only covered the changes since the last notmuch release. There
have been additional changes since nmbug 0.2 (which went out with
notmuch 0.19), and I mention them in the commit message for patch 1/1,
but none of them seemed important enough to call out in NEWS.
I'm also fine leaving these changes out of NEWS and just bumping the
nmbug version (which is why I split this series into two patches).
Cheers,
Trevor
[1]: id:cover.1507675236.git.wking@tremily.us
Subject: [PATCH 0/3] nmbug:
Date: Tue, 10 Oct 2017 15:49:48 -0700
[2]: id: id:20171211174707.GX19165@valgrind.us
Subject: Re: [PATCH 3/4] nmbug: Auto-checkout in clone if it
wouldn't clobber
Date: Mon, 11 Dec 2017 09:47:07 -0800
[3]: id:87a7ypdm3p.fsf@tesseract.cs.unb.ca
Subject: Re: [PATCH 3/4] nmbug: Auto-checkout in clone if it
wouldn't clobber
Date: Mon, 11 Dec 2017 16:51:38 -0400
W. Trevor King (2):
nmbug: Bump to version 0.3
NEWS: Add nmbug 0.3 release notes to the notmuch 0.26 section
NEWS | 13 +++++++++++++
devel/nmbug/nmbug | 2 +-
2 files changed, 14 insertions(+), 1 deletion(-)
--
2.13.6
next reply other threads:[~2017-12-28 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 18:11 W. Trevor King [this message]
2017-12-28 18:11 ` [PATCH 1/2] nmbug: Bump to version 0.3 W. Trevor King
2017-12-31 12:57 ` David Bremner
2017-12-28 18:11 ` [PATCH 2/2] NEWS: Add nmbug 0.3 release notes to the notmuch 0.26 section W. Trevor King
2017-12-29 15:33 ` [PATCH 0/2] nmbug: Bump to 0.3 and document in NEWS Tomi Ollila
2017-12-29 20:58 ` Daniel Kahn Gillmor
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=cover.1514484376.git.wking@tremily.us \
--to=wking@tremily.us \
--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).