jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-18 15:00:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

CODING: update guidance on using the git tree

Browse Source 
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 <mmeffie@sinenomine.net>
Reviewed-by: Mark Vitale <mvitale@sinenomine.net>
Reviewed-by: Cheyenne Wills <cwills@sinenomine.net>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
Tested-by: Benjamin Kaduk <kaduk@mit.edu>
This commit is contained in:
Benjamin Kaduk 2024-03-24 19:54:04 -07:00
parent 665e30f74d
commit c6129a9895
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CODING
View File

@ -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