From: Mark Walters <markwalters1009@gmail.com>
To: Tomi Ollila <tomi.ollila@iki.fi>,
David Bremner <david@tethera.net>,
notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: second freeze for 0.16, now with more freezieness
Date: Sun, 21 Jul 2013 22:33:52 +0100 [thread overview]
Message-ID: <87txjnegxr.fsf@qmul.ac.uk> (raw)
In-Reply-To: <m238r71vpm.fsf@guru.guru-group.fi>
On Sun, 21 Jul 2013, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> On Sat, Jul 20 2013, David Bremner <david@tethera.net> wrote:
>
>> David Bremner <david@tethera.net> writes:
>>
>>> Hi Gang;
>>>
>>> I'll be off the grid for about 12 days, starting on Friday. I thought
>>> that made pretty good sense as a freeze time. On the other hand, I
>>> realize people may have a few last minute items (hopefully small) for
>>> 0.16, so I will consider such suggestions when I get back.
>>>
>>
>> I have added 5 more patches to the release (and master) branch, including
>> jrollins' crypto bugfix. Hopefully this is very close to release, please
>> test.
>
> I'd say 1fd1e57 (with some NEWS) is good for release. I've been running
> 3484372 w/ id:1374163617-23740-1-git-send-email-tomi.ollila@iki.fi
>
> Since 3484372 was pushed and this has been working fine (i.e. the same
> from testing perspective).
What about adding
id:1372976299-30389-1-git-send-email-markwalters1009@gmail.com to the
release branch (but not trunk). Then whatever correct fix we decide on
can go in later and we avoid a potential string of bug reports from
0.16?
Best wishes
Mark
next prev parent reply other threads:[~2013-07-21 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 3:56 soft freeze for 0.16 David Bremner
2013-07-20 12:41 ` second freeze for 0.16, now with more freezieness David Bremner
2013-07-21 20:53 ` Tomi Ollila
2013-07-21 21:33 ` Mark Walters [this message]
2013-07-22 1:12 ` David Bremner
2013-07-28 18:03 ` David Bremner
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=87txjnegxr.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=david@tethera.net \
--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).