Re: consistency in message strings

2020-04-24 Thread Vincent Lefevre
On 2020-04-24 10:28:17 -0500, Derek Martin wrote: > On Fri, Apr 24, 2020 at 09:57:59AM -0500, Derek Martin wrote: > > This is not completely accurate, at least under US law. If you keep a > > mix of old and new content, your copyright date may be a range of > > years instead of a single year. You

Re: consistency in message strings

2020-04-24 Thread Derek Martin
On Fri, Apr 24, 2020 at 09:57:59AM -0500, Derek Martin wrote: > > Also note that year ranges (or list of years) are ambiguous. For > > instance, this version of Mutt is not the one that was published > > in 1996. The copyright notice should normally give only the year > > of the first publication,

Re: consistency in message strings

2020-04-24 Thread Derek Martin
On Fri, Apr 24, 2020 at 04:16:00PM +0200, Vincent Lefevre wrote: > On 2020-04-23 13:29:54 -0500, Derek Martin wrote: > > On Mon, Apr 20, 2020 at 08:09:08PM +0200, ilf wrote: > > > I think it's fair to honor Kevin as maintainer more than "others". > > > I would propose something along: "Copyright (C

Bytes size display

2020-04-24 Thread Vincent Lefevre
I have a couple of remarks about "Bytes size display". There should be an option so that the unit "K" is not displayed when $size_show_bytes is unset. Or perhaps it should never be displayed in this case (i.e. no displayed unit = default unit). In particular, the "K" is a waste of space when both

Re: consistency in message strings

2020-04-24 Thread Vincent Lefevre
On 2020-04-23 13:29:54 -0500, Derek Martin wrote: > On Mon, Apr 20, 2020 at 08:09:08PM +0200, ilf wrote: > > I think it's fair to honor Kevin as maintainer more than "others". > > I would propose something along: "Copyright (C) 1996-2016 Michael > > R. Elkins, 20XX to 2020 Kevin J. McCarthy, and ot