svn commit: r315948 - in head: bin/csh contrib/tcsh contrib/tcsh/config contrib/tcsh/nls contrib/tcsh/nls/C contrib/tcsh/nls/et contrib/tcsh/nls/finnish contrib/tcsh/nls/french contrib/tcsh/nls/ger...

[O. Hartmann]

On Sun, 26 Mar 2017 16:07:57 -0700
Ngie Cooper <yaneurabeya at gmail.com> wrote:

> > On Mar 25, 2017, at 13:19, Chagin Dmitry <dchagin at freebsd.org> wrote:
> >   
> >> On Sat, Mar 25, 2017 at 10:45:30AM -0700, Ngie Cooper wrote:
> >>   
> >>> On Mar 25, 2017, at 06:32, Dmitry Chagin <dchagin at FreeBSD.org> wrote:
> >>> 
> >>> Author: dchagin
> >>> Date: Sat Mar 25 13:32:28 2017
> >>> New Revision: 315948
> >>> URL: https://svnweb.freebsd.org/changeset/base/315948
> >>> 
> >>> Log:
> >>> Update to tcsh 6.20.00  
> >> 
> >> Relnotes: yes
> >>   
> > don't think it matters,
> >   
> >> Should this be MFCed?
> >>   
> > I did not plan  
> 
> Hi Dmitry,
> 
> That's unfortunate :(..
> 
> - Release notes help various groups determining/mitigating risk when
> upgrading FreeBSD. In particular, if you're a consumer of tcsh, a new version
> could break existing scripts, or alternatively, make them work better(/with
> less hacks).
> - MFCing changes like this would be incredibly helpful. In theory, new
> versions should result in a combination of bugfixes to existing features and
> enhancements.
> - It makes it easier to deal with toolchain upgrades.
> - In theory, if the version of the newer forked/tip branch is equivalent to
> the older forked branch, it's easier to assume that the behavior on the two
> branches is equivalent. Personally, I don't care too much about *csh, but I
> know people that do, and I work for a company that kind of does, because it
> affects users logging into our appliances. Thanks! -Ngie
> _______________________________________________ svn-src-head at freebsd.org
> mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head
> To unsubscribe, send any mail to "svn-src-head-unsubscribe at freebsd.org"

+1

Kind regards,

oh