[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Changes to forw(1)
From: |
David Levine |
Subject: |
Re: [Nmh-workers] Changes to forw(1) |
Date: |
Mon, 10 Oct 2016 10:09:49 -0400 |
Ralph wrote:
> +1. The `Forward' header is grabbing another one for nmh's use, in
> addition to the existing `Attach'. Should we be using `Nmh-Forward' if
> the user isn't likely to have the hassle of typing them most of the
> time?
Absolutely. The existing code allows either Nmh-Attach or Attach.
We should use only Nmh-Forward here.
David
- Re: [Nmh-workers] Changes to forw(1), (continued)
- Re: [Nmh-workers] Changes to forw(1), Ralph Corderoy, 2016/10/10
- Re: [Nmh-workers] Changes to forw(1), Valdis . Kletnieks, 2016/10/11
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/11
- Re: [Nmh-workers] Changes to forw(1), Valdis . Kletnieks, 2016/10/11
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/11
- Re: [Nmh-workers] Changes to forw(1), bergman, 2016/10/10
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/10
- Re: [Nmh-workers] Changes to forw(1), Paul Fox, 2016/10/10
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/10
- Re: [Nmh-workers] Changes to forw(1), Lyndon Nerenberg, 2016/10/10
Re: [Nmh-workers] Changes to forw(1),
David Levine <=
Re: [Nmh-workers] Changes to forw(1), norm, 2016/10/10
Re: [Nmh-workers] Changes to forw(1), Lyndon Nerenberg, 2016/10/10