From nobody Thu Mar 23 06:42:31 2023 X-Original-To: current@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 4Phwkq6kljz40wkH for ; Thu, 23 Mar 2023 06:42:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 4Phwkq4tD9z3k9L for ; Thu, 23 Mar 2023 06:42:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x534.google.com with SMTP id x3so82202319edb.10 for ; Wed, 22 Mar 2023 23:42:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1679553762; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=i+05g7voF77ttUlrvoFSyi27GFz1wrwuaZ+2Msw1fbA=; b=BZiAUGSQna26TOiuy2o7gvI9PIPwpP6rJ9QZqbanIegRus0TKZd32a37stf3BQQ+qI O+8+X4oXyIWjvFoZPzuMW9w34jj4bi0vbo52F5et/SIurRWGeh9K4veAH3YAoAtexEMK UNfAh7P6eukIT3occuCYe5De625GYXyt/mpl9BEOXqykU9+Kmyf39np1bTP+/PUKWNtu 01HqBy5VpTGluHfKHacP/45x+KAt906IDbhkbUi/fQAmYSfSBJ0eE1iZPQqKpbR88bRb 50Bl3GcAEa70g330PZSj9/jlbVlcgDTRKPDs4tBengWjtoaApcjJOQBQC9PBc6dhlVJq avzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679553762; 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=i+05g7voF77ttUlrvoFSyi27GFz1wrwuaZ+2Msw1fbA=; b=qiYvbZeWPvOkbdNuA3lXy9Dtc+LoLk2NUuc/rhXLXVLMatfiQ1Dz1Juu0T70MHh3uQ Oz6lrL1voFkDlxhQ4gU9jo3WnAz8VrTLdxTJm8xOTpQEC2iKitIlasWaTQwU4ejvhfgk eQamDlYBtn1u7bVs7QWrXtmnMIRfKmCwjNmocx3NWK1IfqnTH9xBXK6QzLK75oPa5mWr MTdFWTdCcP25X2zLqAMyf70i1ovvj818NzVa+wBQ+luRMtC/V5S7fghHdc1dNimzJ0Zk w5xyWUkDOSUec4YCCCut05bS9EPG9dssM2lLgw1x+xWAiv32jP+6yIkrZp8HNiJxl7Je jXfA== X-Gm-Message-State: AO0yUKUewHBFWZAUoXwNPMVouD7W+5K+/V/GqaS1LiGCJNGy0jUs19Vf 9xi6Y2LczEkEykdPzny9rvTtX8RtvfTvgEnoPxd77Q== X-Google-Smtp-Source: AK7set+a+xHdhs/NFQpr7cziwP2tP6cJPsaJlMrXRlYvPeXyD6Z8Q5LWyuNSE4DWlaIHdrASUtjhFKp1H7H4BhtqRsE= X-Received: by 2002:a05:6402:278e:b0:501:dfd8:67c5 with SMTP id b14-20020a056402278e00b00501dfd867c5mr3568215ede.3.1679553762175; Wed, 22 Mar 2023 23:42:42 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <3e8f96c9-70dc-23ce-cb10-8fb9e32242ca@aetern.org> In-Reply-To: From: Warner Losh Date: Thu, 23 Mar 2023 00:42:31 -0600 Message-ID: Subject: Re: dangling symlinks in openzfs import To: obrien@freebsd.org Cc: Yuri , Martin Matuska , current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000603ef705f78b95ca" X-Rspamd-Queue-Id: 4Phwkq4tD9z3k9L X-Spamd-Bar: ---- 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-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000603ef705f78b95ca Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 23, 2023 at 12:22=E2=80=AFAM David O'Brien = wrote: > On Tue, Mar 21, 2023 at 11:39:11PM +0100, Yuri wrote: > > These have been in there for quite some time now, and every time I > > try to grep something I see this (I know about -s option, but it's > > there in opengrok and other tools output as well): > > grep: > sys/contrib/openzfs/contrib/debian/openzfs-zfsutils.zfs-load-key.init: > > No such file or directory > > Yes! Please someone delete them, or tell me the vendor workflow > approved way of doing the task myself. > > I'd have fixed them myself if we were still using Subversion, but I > don't know the correct way to handle them in the vendor branching > within Git. > Going rogue and stepping on the OpenZFS maintainer is rather antisocial. Good thing you can't be bothered to read the current documentation on vendor branches. All sarcasm aside, that's really not a productive attitude. Warner --000000000000603ef705f78b95ca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Mar 23, 2023 at 12:22=E2=80= =AFAM David O'Brien <obrien@fr= eebsd.org> wrote:
On Tue, Mar 21, 2023 at 11:39:11PM +0100, Yuri wrote:
> These have been in there for quite some time now, and every time I
> try to grep something I see this (I know about -s option, but it's=
> there in opengrok and other tools output as well):
> grep: sys/contrib/openzfs/contrib/debian/openzfs-zfsutils.zfs-load-key= .init:
> No such file or directory

Yes!=C2=A0 Please someone delete them, or tell me the vendor workflow
approved way of doing the task myself.

I'd have fixed them myself if we were still using Subversion, but I
don't know the correct way to handle them in the vendor branching
within Git.

Going rogue and stepping on= the=C2=A0OpenZFS maintainer is rather antisocial.
Good thing you= can't be bothered to read the current documentation on
vendo= r branches.

All sarcasm aside, that's really n= ot a productive attitude.

Warner
--000000000000603ef705f78b95ca--