[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available
From: |
Paul Fox |
Subject: |
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available |
Date: |
Fri, 23 Feb 2018 12:07:41 -0500 |
ken wrote:
> >> > I don't remember that glitch in the past, but it is so minor that I
> >> > might
> >> > well have not noticed or ignored it.
> >> > [...]
> >>
> >> Oh, I guess that's because `scan -v' does not modify `context', e.g.:
> >
> >Right. Neither does -help.
> >
> >Ken, would it be a bad idea to call context_save() in nmh_version_changed()
> >if the Version context is replaced?
>
> Hrm. Part of me says "no, adding that should be fine" ... but, hell,
> I'm not sure, we've been bitten by an unsuspecting change like that
> before. I almost think that things like that should be dealt with more
> generally, like in an exit handler or something. I'm leaning toward
> "not deal with it now". Even we people think we should call context_save()
> in nmh_version_changed(), I don't think this should be fixed for 1.7.1.
> Thoughts?
agreed. doesn't seem like a release blocker to me.
paul
=----------------------
paul fox, address@hidden (arlington, ma, where it's 37.0 degrees)
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available, Leonardo Taccari, 2018/02/22
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available, Ken Hornstein, 2018/02/23
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available,
Paul Fox <=
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available, David Levine, 2018/02/23
Re: [Nmh-workers] Third release candidate for 1.7.1 is now available, Ken Hornstein, 2018/02/23