From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5B7C81F62E for ; Wed, 8 Mar 2023 19:31:56 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=google header.b=OujT1wbu; dkim-atps=neutral Received: by mail-qt1-x829.google.com with SMTP id r16so17703436qtx.9 for ; Wed, 08 Mar 2023 11:31:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; t=1678303915; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=JRFw4qgl368GjzvzBIkosGrP2H6bkCaiI/9tGI0wMLw=; b=OujT1wbuvP2+ya65lO9bbAHtRAGQfyif0856ztpdaJ5ZJbb1/l87uHXijAvQcQnpk0 WiyehGZ8ZOah1pbuD3HdWOwivHF41MJHv5sSuWdTww3TRQmX9OAMyLJm3EUrQkBoCJNT joPbk4uKd9++ifB20zHkvPFvrAWne7jg+L1so= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678303915; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=JRFw4qgl368GjzvzBIkosGrP2H6bkCaiI/9tGI0wMLw=; b=xpRli98RkBy/FX8ClhnaNrpCOm/N57yNfdeIlTynnRyiU9jZCKCkBGJXBl0Aw5Kes+ mYUIGco2x553sbUJ1ZZ9qsHaapwPVAQ7wZUoRyvjIfDyaPPFHo2QclTCGx8/WuiVcvtA ampQxfhcOa7qFunx1q4vbWF9x2p/An9QEkN6Yy+CV6Do3sRIpcKFw16PqChuAe/Q786i hjLPnIKhF0pGns1KMDwreCUVUrVdfV2LicdelY0wfoIB5b7IgQAU93naNG2LPxmzP8K0 MkYxVm8pGhuWUovJtXVq+R6tgkGZMIPLcbiC9K9yAfIDcY/fFW+v84jwwCVCNswbealw pa1w== X-Gm-Message-State: AO0yUKV+dZEA6nioB6DBPzgzZkD6RQo7uz8gZ8OAAGTPQKfg/oVmnbXE SLau3CnLUIWph8K/F8XEuImVkg== X-Google-Smtp-Source: AK7set+iKoQSq2DAx/9R1Cqv9qQ/4Zgfj9m+nnjZ1XTz557+5OJPwtY6a03603FkkHBtJggYHSrVcA== X-Received: by 2002:ac8:7f49:0:b0:3bf:d184:7ca2 with SMTP id g9-20020ac87f49000000b003bfd1847ca2mr30955004qtk.21.1678303914971; Wed, 08 Mar 2023 11:31:54 -0800 (PST) Received: from nitro.local (bras-base-mtrlpq5031w-grc-30-209-226-106-7.dsl.bell.ca. [209.226.106.7]) by smtp.gmail.com with ESMTPSA id q41-20020a05620a2a6900b0074341cb30d0sm6604611qkp.62.2023.03.08.11.31.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Mar 2023 11:31:54 -0800 (PST) Date: Wed, 8 Mar 2023 14:31:53 -0500 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: [PATCH] lei_mirror: unlink FETCH_HEAD when fetching forkgroups Message-ID: <20230308193153.hcx6jl727e5t7cwj@nitro.local> References: <20230308110258.525501-1-e@80x24.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230308110258.525501-1-e@80x24.org> List-Id: On Wed, Mar 08, 2023 at 11:02:58AM +0000, Eric Wong wrote: > Apparently, --no-write-fetch-head is broken in current git[1]. > It also wasn't in older git, at all. So just unlink FETCH_HEAD > as we see it, but keep using --no-write-fetch-head to avoid the > syscall and I/O overhead when we can. I'm pretty sure --no-write-fetch-head was added in response to me asking why it's needed for bare repos in the first place. In grokmirror, we symlink it to /dev/null, but you already know this probably. -K