Date: Sun, 26 Aug 2001 15:00:09 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Kaila <kaila@o-o.org>, Mike Smith <msmith@FreeBSD.ORG>, Kris Kennaway <kris@obsecurity.org>, Jim Bryant <kc5vdj@yahoo.com>, freebsd-current@FreeBSD.ORG Subject: Re: Why is csh tcsh? This can be a bad thing... Message-ID: <3B897169.79A29D82@mindspring.com> References: <200108261958.f7QJwLr02345@mass.dis.org> <Pine.BSF.4.21.0108261453540.59262-100000@o-o.org> <20010826134326.A29583@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > On Sun, Aug 26, 2001 at 02:57:31PM -0500, Kaila wrote: > > Naming linking it to csh broke things for people who weren't > > informed it was happeneing, and then had to go and spend hours > > tracking down the problem and fixing it. > > How could you be uninformed about this change? The csh vs. tcsh > bikeshed happen 16 months ago in the freebsd-current mailing list. > Speaking up 16 months later is an unusual way to let the developers > know you have an opinion on this change. The bikeshed was not cross-posted to -stable or -hackers, and someone did an "MFC" on the change, thus bypassing any discussion about getting the change into -stable? Or the natural progression of version changes pushed the change event into the next release, with no real notification, and no "csh is deprecated; used tcsh instead" message for one major release (i.e. there was no formal deprecation during which people could change their csh scripts)? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B897169.79A29D82>