From c6129a989554c1374496d8c0b33a32f90b87009b Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Sun, 24 Mar 2024 19:54:04 -0700 Subject: [PATCH] CODING: update guidance on using the git tree We don't really need a "Danger Will Robinson"-style warning at this point. Also update the browsing URL to use TLS (https://). Change-Id: I102b8bd8a8c91c68d6d6383ea146a0cb57b8d571 Reviewed-on: https://gerrit.openafs.org/15716 Reviewed-by: Michael Meffie Reviewed-by: Mark Vitale Reviewed-by: Cheyenne Wills Reviewed-by: Benjamin Kaduk Tested-by: Benjamin Kaduk --- CODING | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/CODING b/CODING index 98e1e33a2c..66fdc02086 100644 --- a/CODING +++ b/CODING @@ -204,13 +204,10 @@ way to do this?) GIT Usage ========= -*WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* -The Git tree may not always have code which can currently be built. -While every effort is made to keep the head of the tree buildable, -you may at any time find yourself between commits and hence have a tree -which does not build, or worse, causes more serious problems! - -Do not use the Git tree unless you know what you're doing. +With the broad continuous integration coverage provided by buildbot +and the current code review policy for changes entering master, it's +generally expected that the development branch will be buildable and +functional at any given time. Git checkouts do not include files generated by autoconf. You can run regen.sh (at the top level) to create these files. You will need @@ -219,7 +216,7 @@ to have autoconf and automake installed on your system. Summary ------- -Browse: http://git.openafs.org/ +Browse: https://git.openafs.org/ Clone: git clone git://git.openafs.org/openafs.git Step-by-step