From owner-freebsd-git@freebsd.org Thu Jan 28 15:17:34 2021 Return-Path: Delivered-To: freebsd-git@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 52159527342 for ; Thu, 28 Jan 2021 15:17:34 +0000 (UTC) (envelope-from stsp@stsp.name) Received: from einhorn-mail-out.in-berlin.de (einhorn-mail-out.in-berlin.de [217.197.80.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.in-berlin.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DRPGj3LD7z3k7X for ; Thu, 28 Jan 2021 15:17:33 +0000 (UTC) (envelope-from stsp@stsp.name) X-Envelope-From: stsp@stsp.name Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 10SFHSa7012111 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 28 Jan 2021 16:17:30 +0100 Received: from localhost (byrne.stsp.name [local]) by byrne.stsp.name (OpenSMTPD) with ESMTPA id 4e198532; Thu, 28 Jan 2021 16:17:28 +0100 (CET) Date: Thu, 28 Jan 2021 16:17:28 +0100 From: Stefan Sperling To: Christian Weisgerber Cc: freebsd-git@freebsd.org Subject: Re: git setup/usage question Message-ID: Mail-Followup-To: Christian Weisgerber , freebsd-git@freebsd.org References: <20210126151017.4a9dd711@zeta.dino.sk> <00F58366-4178-458E-8865-E1A2E5324EB4@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4DRPGj3LD7z3k7X X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of stsp@stsp.name has no SPF policy when checking 217.197.80.21) smtp.mailfrom=stsp@stsp.name X-Spamd-Result: default: False [-2.20 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[stsp.name]; RBL_DBL_DONT_QUERY_IPS(0.00)[217.197.80.21:from]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[217.197.80.21:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:29670, ipnet:217.197.80.0/20, country:DE]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-git]; RCVD_IN_DNSWL_LOW(-0.10)[217.197.80.21:from] X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2021 15:17:34 -0000 On Thu, Jan 28, 2021 at 02:07:57PM -0000, Christian Weisgerber wrote: > On 2021-01-28, David Wolfskill wrote: > > > That said, what I set up for my use does involve a "--bare" (more > > precisely, a "--mirror") repo. > > > > I documented what I did at > > https://www.catwhisker.org/~david/FreeBSD/repo-sync.html > > FWIW, a bare repository and checking out any number of worktrees > from it is the normal way Got (devel/got) works. There are a couple of additional aspects of Got which will seem familiar to former CVS/SVN users: - mixed-commit work trees operate just like with SVN, such that 'got update sys/dev/iwm' will do exactly what SVN users expect - relatively small command set with familiar names and options: checkout, update, info, revert -R, ... See the man page for more: https://gameoftrees.org/got.1.html - strong focus on the centralized repository use case; the idea is to store one repository per machine as was done with CVSup/svnsync That said, while this software is functional it is still under development. The current feature set should be more than complete enough to support anyone tracking development sources in a read-only fashion. But we're not ready to set the UI in stone, meaning scripts using Got may break. This is not a "set it up once and forget" solution. New releases occur every couple of weeks and are similar to "-current" snapshots rather than "-stable" releases. For now, I would suggest to stay away from Got unless you like what you see and would want this software to become truly production-ready. Then, by all means, use it and provide feedback to help our progress. Cheers, Stefan