From owner-freebsd-stable@freebsd.org Thu Feb 25 09:30:28 2021 Return-Path: Delivered-To: freebsd-stable@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 27F6555CBAC for ; Thu, 25 Feb 2021 09:30:28 +0000 (UTC) (envelope-from olivier.freebsd@free.fr) Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [IPv6:2a01:e0c:1:1599::15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DmSFH1rG5z4Qnb for ; Thu, 25 Feb 2021 09:30:26 +0000 (UTC) (envelope-from olivier.freebsd@free.fr) Received: from ravel.localnet (unknown [90.118.181.206]) (Authenticated sender: olivier.freebsd@free.fr) by smtp6-g21.free.fr (Postfix) with ESMTPSA id ACD967802C2; Thu, 25 Feb 2021 10:30:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=free.fr; s=smtp-20201208; t=1614245421; bh=RpE48Ef21jJS+DrBp1YLaDHMxhDyATTlWpASj5QLbSg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Zsj6GbH5Pf3BTQPhCIaQNVUvBlNCUpnUNbX9BwxXrNzwHLoiFirj/4ne/qIGgmV1x HVsS3EHjaYcD6pjNx9lyd8Mqwprn9GaxgojmugCha+xCTxY2af9k17TqJiKD4Vgqnt 4tsoQjYF3NC5O6UCdYZIS5oZfVblT4oss9702wojfJYMZlcxq6aEnOXAtC8ftntC+o koEdh+Had+QhnRBQTUvqV1ZZUQHHE0rP0I0nhkyb1MzaOEGErpaBJyD8tBwVZTEjU+ fnZndwQzo5z9CpkJtPHlswYfRCK1f1Dzoo5J/f73DlVUJe/ozAR15d0gyrXus8hcPf gmxA8EZhKpqzw== From: Olivier Certner To: Kevin Oberman Cc: FreeBSD-STABLE Mailing List Subject: Re: How do I know if my 13-stable has security patches? Date: Thu, 25 Feb 2021 10:30:15 +0100 Message-ID: <3308997.ajJYar8FF2@ravel> In-Reply-To: References: <1748076.jFELhIj8lM@ravel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4DmSFH1rG5z4Qnb X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=free.fr header.s=smtp-20201208 header.b=Zsj6GbH5; dmarc=pass (policy=none) header.from=free.fr; spf=pass (mx1.freebsd.org: domain of olivier.freebsd@free.fr designates 2a01:e0c:1:1599::15 as permitted sender) smtp.mailfrom=olivier.freebsd@free.fr X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_FROM(0.00)[free.fr]; R_SPF_ALLOW(-0.20)[+ip6:2a01:e0c:1:1599::15]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[free.fr:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[free.fr,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; CTE_CASE(0.50)[]; FREEMAIL_ENVFROM(0.00)[free.fr]; ASN(0.00)[asn:12322, ipnet:2a01:e00::/26, country:FR]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:e0c:1:1599::15:from]; DWL_DNSWL_NONE(0.00)[free.fr:dkim]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[free.fr:s=smtp-20201208]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[2a01:e0c:1:1599::15:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a01:e0c:1:1599::15:from]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 09:30:28 -0000 > Neither command is what I'd call 'intuitive', so it would have taken me a > long time to find either of them. I cut and pasted the 'git branch' command > and it took me a moment to realize what that meant. Never ran "grep -l" on > a pipe, I guess. You made me laugh! Apart from relatively simple commands, git's interface is far from intuitive. That's the reason why I regret that it became the hugely dominant DVCS. Sure, arguably most of the complexity comes from the DAG of commits, and the need to distinguish what is local and what is remote, which are not specific to git at all. But its interface makes things unnecessarily more complicated. It seems it grew up from ad-hoc pieces without much planification and it took a long time before it finally started to get more attention. A typical case were the cathedral would have been much better than the bazaar: Research for a minimal set of concepts required to have it work and model commands after it. Yes, it's not trivial and it takes time, but is usually much better in the end. But it's progressing somehow. Some time ago, 'git restore ' appeared, to replace the stance 'git checkout -- '. It seems they are also trying to do something with new, hopefully more natural, commands, such as 'git switch' to switch branches. I guess this will benefit the next generations of us, since we have to deal with what's available and works in the meantime (and habits). ;-) And while I'm thinking about it: There is also 'git cherry' to check if some changes are in a branch. It doesn't match on the commit hashes but on the file contents. This is not necessary here because SAs specify the relevant commits per branches, but can be very useful to check that some changes were actually cherry-picked in another branch. -- Olivier Certner