svn commit: r365984 - head/usr.bin/calendar/calendars

Scott Long scottl at samsco.org
Tue Sep 22 20:40:43 UTC 2020


>>>>>> 
>>>>>> Does this file still need to be in FreeBSD? It may have been a novel=
>> ty back
>>>>>> in the day but IMO calendar.history has nothing to do with BSD, comp=
>> uters
>>>>>> or anything else of interest to FreeBSD. At the very least this file=
>> should
>>>>>> be moved to ports or better yet, removed entirely. I simply don't se=
>> e the
>>>>>> point of it being in the tree and distributed with an O/S, any O/S.
>>>> =20
>>>> I think that the only reason for this file's existence in the source tr=
>> ee is for
>>>> Greg's staving off the commit bit reaper.
>>>> No offense meant.
>>>> =20
>>>> P.S.
>>>> And occasional flame wars, it seems.
>>> =20
>>> We already had a similar discussion in march 2020 after r358561 [1].
>>> =20
>>> In the short, the calendar utility has it's historic place, even it's
>>> just more a kind of tradition, like adding yourself as a FreeBSD committer
>>> to calendar.freebsd.
>>> =20
>>> [1] https://lists.freebsd.org/pipermail/svn-src-all/2020-March/thread.html
>> 
>> Would it make sense to prune calendar entries to only BSD-related
>> entries?
> 
> +1
> 
> 

Responding to the most recent message here, but there are a couple of things
that warrant a response.  First, proposals for technical action, like re-arranging
or removing the calendar module, should happen on arch@, not here.  Please
formulate a proposal and move the discuss to that forum.

Second, there’s a vibe in parts of this thread that are passive-aggressively
disrespectful to Greg.  I encourage those who might feel some personal
frustration towards Greg to talk to him directly.  The Core team can help with
that communication if needed.  Otherwise, it’s not not appropriate and not
welcome on the mailing lists.  If you don’t feel it’s important enough to
resolve in a professional manner, then please keep it to yourself.

Thanks,
Scott



More information about the svn-src-all mailing list