Date: Tue, 21 Nov 2023 11:09:57 -0700 From: Warner Losh <imp@bsdimp.com> To: Brooks Davis <brooks@freebsd.org> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Time to remove sccs tags Message-ID: <CANCZdfq-O69ZLPGjTpRWK=thwx7AwQe6u9LQNLO2YNtsyAOzog@mail.gmail.com> In-Reply-To: <ZVzw7UknA_qq2FK6@spindle.one-eyed-alien.net> References: <CANCZdfo5Pj=AWmd5ftZ6OmMXBrkFAbZnYZt8EC8EqRqoi9csHw@mail.gmail.com> <ZVzw7UknA_qq2FK6@spindle.one-eyed-alien.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Nov 21, 2023, 11:03 AM Brooks Davis <brooks@freebsd.org> wrote: > On Tue, Nov 21, 2023 at 09:12:48AM -0700, 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? > > Yes please. The history is there in there repo(s) and there's so much > blind copying where the context is entirely lost. > > From my perspective it would be nice to have fewer commits per-subtree > than with $FreeBSD removal. In recent spelunking I've found that for low > traffic sub-trees I'm seeing a full screen (~50 lines for me) or more of > those > logs before getting to commits with content changes due to inconsistent > formatting leading to multiple removal commits. > Fortunately there are way fewer files like this so I can do fewer commits that are still macabre. Warner > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 21, 2023, 11:03 AM Brooks Davis <<a href="mailto:brooks@freebsd.org">brooks@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Nov 21, 2023 at 09:12:48AM -0700, Warner Losh wrote:<br> > It's been 30 odd years since the last csrg release. They are no more.<br> > <br> > At this point I think we can safely remove the few sccs tags that remain in<br> > the tree. The data will be there in git if we ever need it.<br> > <br> > Comments?<br> <br> Yes please. The history is there in there repo(s) and there's so much<br> blind copying where the context is entirely lost.<br> <br> >From my perspective it would be nice to have fewer commits per-subtree<br> than with $FreeBSD removal. In recent spelunking I've found that for low<br> traffic sub-trees I'm seeing a full screen (~50 lines for me) or more of those<br> logs before getting to commits with content changes due to inconsistent<br> formatting leading to multiple removal commits.<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Fortunately there are way fewer files like this so I can do fewer commits that are still macabre.</div><div dir="auto"><br></div><div dir="auto">Warner</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote></div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfq-O69ZLPGjTpRWK=thwx7AwQe6u9LQNLO2YNtsyAOzog>