From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 187AF1F454 for ; Fri, 8 Nov 2019 16:08:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726232AbfKHQIg (ORCPT ); Fri, 8 Nov 2019 11:08:36 -0500 Received: from smtp.hosts.co.uk ([85.233.160.19]:31436 "EHLO smtp.hosts.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726036AbfKHQIg (ORCPT ); Fri, 8 Nov 2019 11:08:36 -0500 Received: from [92.30.121.54] (helo=[192.168.1.22]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1iT6oM-0006mz-3j; Fri, 08 Nov 2019 16:08:34 +0000 Subject: Re: No Checkout / Read Only config Flag To: Ingo Wolf , Git List References: From: Philip Oakley Message-ID: Date: Fri, 8 Nov 2019 16:08:35 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On 07/11/2019 21:34, Ingo Wolf wrote: > Hi, > > is there a readonly / no checkout flag in the git configs? > Not that I'm aware of, but the use-case isn't clear, and is perhaps contrary to actually having a version management system > I use Git to trace / Backup some worktrees and would like to prevent > changing them accidentally with git. > How would such 'accidents' happen? What's the size of the worktree and how do you do such an accidental commit? I could see that if you are changing hundreds of files within a commit, and only one or two files need preserved, then did a `git add -A` you would include any changes to those one or two special files, which needed special attention. This feels similar but not quite the same as previous discussions about 'precious' files (the latter commonly being untracked/ignored, but shouldn't be removed/cleaned). Technology won't solve the human error modes..., though a clear use case can help. -- Philip