From nobody Tue Nov 21 18:09:57 2023 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZXTt4YVBz523SP for ; Tue, 21 Nov 2023 18:10:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZXTt45Xkz4lmD for ; Tue, 21 Nov 2023 18:10:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-9c773ac9b15so801911866b.2 for ; Tue, 21 Nov 2023 10:10:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1700590209; x=1701195009; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JV0Q3ZsJmg2+2DNAPgdkxJQRo5vl2U9M7U9DoR7OIY8=; b=XjLWAa6QapNvrem8Zz1qugMyQ4baml0Ys9I+jlEaI6KqqWbbjgXrROwFHq89xs/ZMw k+3Yg+lsX28qmiBoUkTRoWd4i+dm39rnihIWFAbbGoO1drId+Zj66pMCAQIg3vXC73Qb 1swoUxPi78x45j7l7HUwBlBMarSBKXKR4PzeUu0GJ3BgcdIU+kLdD8MJvgZOJL7yE99E Grl29CAVlB0pMFikX+25P5X9BK25YVejtqT2JcEIHYbcPwi7C8CsU8Qd6c7z5swxVB3J L8YBjzK4Ep4nPSXpAd0LJXYw0gMZFL/B5IzAJ5Z9M9IG4ylgQBm1Z8wfbVseJRe8exoU kY8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700590209; x=1701195009; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JV0Q3ZsJmg2+2DNAPgdkxJQRo5vl2U9M7U9DoR7OIY8=; b=ZRG2N+QSpdZfPEu09xMhAOPrt9n3Zjbrc2tAuUgXjn6BhRFsqI0I3+3gY2Z3CA3QWy whI7//FcaqqcUwKeQqYEm/Ls2IG2cyFyAgs4O2JFMCBQ9QctzelPfl+Ihd5dq7yEsOvd KXK6IuNDatdpoW9mZxrocifEMS7YiJAd1YxoaioparYPF2JIHaNDl/Z07KH2nzSJUgC1 IQEZcLtvRhV6V2Er/l5SOKE17K9C5R/Q2DePvcNGHS0fP7NIMLq8v9dlyWZFqgAbi97W xw6w+pBcST34KO+cx7C6CJGM4R+HJQyhaOp9di5uX0PVhZdIsb3L9PxVx+2Q7/LI63J+ YFJg== X-Gm-Message-State: AOJu0Yxx9XyQ/ccoT4TF1EfO5ikxNjYnWv2TwUDsqB/r/b82cxGxnIwV DXhNpPmGjJsUYhrhXsnznu3lvf7+J69eew6OEJ1L96xsHNEKta6p X-Google-Smtp-Source: AGHT+IE/YW4nL01gHsq3yF8J0ZtTTWJHCQFQA58+tZVGk394EbN+J88qdpBw0xXhpmf7mNwQn9+yR6KWizBgGgbHYkE= X-Received: by 2002:a17:906:2290:b0:9a1:891b:6eed with SMTP id p16-20020a170906229000b009a1891b6eedmr6755499eja.76.1700590209011; Tue, 21 Nov 2023 10:10:09 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Tue, 21 Nov 2023 11:09:57 -0700 Message-ID: Subject: Re: Time to remove sccs tags To: Brooks Davis Cc: "freebsd-arch@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000005123d2060aad8371" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SZXTt45Xkz4lmD --0000000000005123d2060aad8371 Content-Type: text/plain; charset="UTF-8" On Tue, Nov 21, 2023, 11:03 AM Brooks Davis 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 > --0000000000005123d2060aad8371 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Nov 21, 2023, 11:03 AM Brooks Davis <brooks@freebsd.org> wrote:
=
On Tue, Nov 21, 2023 at 09:12:48AM -0700, Wa= rner Losh wrote:
> It's been 30 odd years since the last csrg release. They are no mo= re.
>
> At this point I think we can safely remove the few sccs tags that rema= in in
> the tree. The data will be there in git if we ever need it.
>
> Comments?

Yes please.=C2=A0 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.=C2=A0 In recent spelunking I've found that = for low
traffic sub-trees I'm seeing a full screen (~50 lines for me) or more o= f those
logs before getting to commits with content changes due to inconsistent
formatting leading to multiple removal commits.

Fortunately there are way fe= wer files like this so I can do fewer commits that are still macabre.
=

Warner
--0000000000005123d2060aad8371--