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
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,
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
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
On Mon, Apr 20, 2020 at 08:09:08PM +0200, ilf wrote:
> Vincent Lefevre:
> > > > Copyright (C) 1996-2016 Michael R. Elkins and others.
> > > Thanks, but what should it be updated to say? Michael Elkins hasn't
> > > contributed since 2016. Is it correct to swap the date to 2020, or
> > > should I i
On 2020-04-22 20:34:18 -0400, re...@webconquest.com wrote:
> Maybe add a line pointing to the COPYRIGHT file or perhaps a link to
> somewhere on the website?
It already does by mentioning "mutt -vv".
> I was thinking perhaps an option would be to look at the number of lines
> contributed, but wit
On Mon, Apr 20, 2020 at 01:14:40PM -0700, Kevin wrote in
<20200420201440.gg17...@afu.lan>:
On Mon, Apr 20, 2020 at 08:20:08PM +0100, Steve Karmeinsky wrote:
I’d agree with that sentiment
Thank you ilf and Steve.
But the phrase "standing on the shoulders of giants" is very true in
this case.
On Mon, Apr 20, 2020 at 08:20:08PM +0100, Steve Karmeinsky wrote:
I’d agree with that sentiment
Thank you ilf and Steve.
But the phrase "standing on the shoulders of giants" is very true in
this case. I could never make anything as awesome as Mutt on my own.
I would be embarrassed to put m
I’d agree with that sentiment
Steve
--
Sent from my iPhone
> On 20 Apr 2020, at 19:09, ilf wrote:
>
> Vincent Lefevre:
Copyright (C) 1996-2016 Michael R. Elkins and others.
>>> Thanks, but what should it be updated to say? Michael Elkins hasn't
>>> contributed since 2016. Is it cor
Vincent Lefevre:
Copyright (C) 1996-2016 Michael R. Elkins and others.
Thanks, but what should it be updated to say? Michael Elkins hasn't
contributed since 2016. Is it correct to swap the date to 2020, or should I
instead change the line to show my copyright?
Michael Elkins hasn't contribu
On Mon, Apr 20, 2020 at 07:08:34PM +0200, Vincent Lefevre wrote:
On 2020-04-20 09:14:22 -0700, Kevin J. McCarthy wrote:
On Mon, Apr 20, 2020 at 04:13:08PM +0200, Vincent Lefevre wrote:
> BTW, about copyright years, "mutt -v" says:
>
> [...]
> Copyright (C) 1996-2016 Michael R. Elkins and others.
On 2020-04-20 09:14:22 -0700, Kevin J. McCarthy wrote:
> On Mon, Apr 20, 2020 at 04:13:08PM +0200, Vincent Lefevre wrote:
> > BTW, about copyright years, "mutt -v" says:
> >
> > [...]
> > Copyright (C) 1996-2016 Michael R. Elkins and others.
> > [...]
> >
> > This should be updated.
>
> Thanks,
On Mon, Apr 20, 2020 at 04:13:08PM +0200, Vincent Lefevre wrote:
BTW, about copyright years, "mutt -v" says:
[...]
Copyright (C) 1996-2016 Michael R. Elkins and others.
[...]
This should be updated.
Thanks, but what should it be updated to say? Michael Elkins hasn't
contributed since 2016.
On 2020-04-19 19:03:19 -0700, Kevin J. McCarthy wrote:
> On Mon, Apr 20, 2020 at 03:47:51AM +0200, Vincent Lefevre wrote:
> > I have noticed a lack of consistency in message strings:
> > * "GPG key" vs "gpg key" (this should be "GPG key")
On Mon, Apr 20, 2020 at 12:35:58PM +0900, Tamo wrote:
The source almost always calls them "op(erator)s" while the manual "modifiers."
So it's not surprising that developers make an inconsistency in this case.
Hi Tamo,
Yes, I didn't pay enough attention to consistency. Thanks (and to
Vincent
Hi mutt-dev,
On Mon, Apr 20, 2020 at 11:03 AM Kevin J. McCarthy wrote:
>
> On Mon, Apr 20, 2020 at 03:47:51AM +0200, Vincent Lefevre wrote:
> >I have noticed a lack of consistency in message strings:
> > * "GPG key" vs "gpg key" (this should be "GPG
On Mon, Apr 20, 2020 at 03:47:51AM +0200, Vincent Lefevre wrote:
I have noticed a lack of consistency in message strings:
* "GPG key" vs "gpg key" (this should be "GPG key")
* "compose session" vs "editing session"
Moreover, I think that &
Hi,
I have noticed a lack of consistency in message strings:
* "GPG key" vs "gpg key" (this should be "GPG key")
* "compose session" vs "editing session"
Moreover, I think that "autocrypt" should be written with a capital
letter (Au
18 matches
Mail list logo
