Date: Tue, 21 Nov 2023 23:03:23 -0700 From: Warner Losh <imp@bsdimp.com> To: Philip Paeps <philip@freebsd.org> Cc: Robert Clausecker <fuz@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: Time to remove sccs tags Message-ID: <CANCZdfq%2BPqyppQkKo1hOXaaiDxgq6cFV7ENEgPF9xBqW-C5LCQ@mail.gmail.com> In-Reply-To: <1CA7956B-8204-4328-A977-C874A3FAE0A7@freebsd.org> References: <CANCZdfo5Pj=AWmd5ftZ6OmMXBrkFAbZnYZt8EC8EqRqoi9csHw@mail.gmail.com> <22458D4C-35ED-4040-AAA1-A43006C0B32F@freebsd.org> <ZV2P164Qhq8r7gK3@fuz.su> <1CA7956B-8204-4328-A977-C874A3FAE0A7@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000d73597060ab7791d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Nov 21, 2023 at 10:41=E2=80=AFPM Philip Paeps <philip@freebsd.org> = wrote: > On 2023-11-22 13:21:27 (+0800), Robert Clausecker wrote: > > Am Wed, Nov 22, 2023 at 01:15:14PM +0800 schrieb Philip Paeps: > >> On 2023-11-22 00:12:48 (+0800), Warner Losh wrote: > >>> It's been 30 odd years since the last csrg release. They are no > >>> more. > >>> > >>> At this point I think we can safely remove the few sccs tags that > >>> remain > >>> in > >>> the tree. The data will be there in git if we ever need it. > >>> > >>> Comments? > >> > >> Long overdue. > >> > >> Since we're removing all these tags, should we also remove what(1) > >> and > >> possibly ident(1) from the tree? > >> > >> Removing what(1) should be non-controversial at this stage. I can > >> imagine > >> some people may still be using ident(1) on extant Subversion systems. > > > > what(1) is part of POSIX, though I guess you can just install > > devel/sccs > > if you need it. > > I think the only reason we still have what(1) is because it was once > useful to (help) identify the provenance of a file. It wasn't very good > at it in the past, and it certainly isn't very good at it now. > what is not going anywhere: % what /boot/kernel/kernel /boot/kernel/kernel: FreeBSD 14.0-ALPHA3 amd64 1400097 #27 stable/14-n265023-7be29291845a: Sun Aug 27 12:46:22 MDT 2023 % > In 2002, Juli tried to resurrect SCCS for POSIX/SUS compliance. It > looks like the attempt was aborted before FreeBSD 5.0-RELEASE though... > > Anyone who needs to tick this box in their standards compliance > paperwork should simply install devel/sccs. :) > What also works with kernel core files. Warner > Philip > > -- > Philip Paeps > Senior Reality Engineer > Alternative Enterprises > --000000000000d73597060ab7791d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 21, 2023 at 10:41=E2=80= =AFPM Philip Paeps <<a href=3D"mailto:philip@freebsd.org">philip@freebsd= .org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar= gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1= ex">On 2023-11-22 13:21:27 (+0800), Robert Clausecker wrote:<br> > Am Wed, Nov 22, 2023 at 01:15:14PM +0800 schrieb Philip Paeps:<br> >> On 2023-11-22 00:12:48 (+0800), Warner Losh wrote:<br> >>> It's been 30 odd years since the last csrg release. They a= re no <br> >>> more.<br> >>><br> >>> At this point I think we can safely remove the few sccs tags t= hat <br> >>> remain<br> >>> in<br> >>> the tree. The data will be there in git if we ever need it.<br= > >>><br> >>> Comments?<br> >><br> >> Long overdue.<br> >><br> >> Since we're removing all these tags, should we also remove wha= t(1) <br> >> and<br> >> possibly ident(1) from the tree?<br> >><br> >> Removing what(1) should be non-controversial at this stage.=C2=A0 = I can <br> >> imagine<br> >> some people may still be using ident(1) on extant Subversion syste= ms.<br> ><br> > what(1) is part of POSIX, though I guess you can just install <br> > devel/sccs<br> > if you need it.<br> <br> I think the only reason we still have what(1) is because it was once <br> useful to (help) identify the provenance of a file.=C2=A0 It wasn't ver= y good <br> at it in the past, and it certainly isn't very good at it now.<br></blo= ckquote><div><br></div><div>what is not going anywhere:</div><div><br></div= ><div>% what /boot/kernel/kernel<br>/boot/kernel/kernel:<br> FreeBSD 14.0-A= LPHA3 amd64 1400097 #27 stable/14-n265023-7be29291845a: Sun Aug 27 12:46:22= MDT 2023<br></div><div>%</div><div>=C2=A0<br></div><blockquote class=3D"gm= ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,= 204,204);padding-left:1ex"> In 2002, Juli tried to resurrect SCCS for POSIX/SUS compliance.=C2=A0 It <b= r> looks like the attempt was aborted before FreeBSD 5.0-RELEASE though...<br> <br> Anyone who needs to tick this box in their standards compliance <br> paperwork should simply install devel/sccs. :)<br></blockquote><div><br></d= iv><div>What also works with kernel core files.</div><div><br></div><div>Wa= rner<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m= argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left= :1ex"> Philip<br> <br> -- <br> Philip Paeps<br> Senior Reality Engineer<br> Alternative Enterprises<br> </blockquote></div></div> --000000000000d73597060ab7791d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfq%2BPqyppQkKo1hOXaaiDxgq6cFV7ENEgPF9xBqW-C5LCQ>