[Cryptech-Commits] [releng/alpha] branch master updated: README.md explained package build steps in the wrong order.

[git at cryptech.is]

This is an automated email from the git hooks/post-receive script.

sra at hactrn.net pushed a commit to branch master
in repository releng/alpha.

The following commit(s) were added to refs/heads/master by this push:
     new 8cef915  README.md explained package build steps in the wrong order.
8cef915 is described below

commit 8cef9151f6fd927aa31cb07215c87264f29441b8
Author: Rob Austein <sra at hactrn.net>
AuthorDate: Mon May 15 14:20:10 2017 -0400

    README.md explained package build steps in the wrong order.
---
 README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 42f3b76..b8920db 100644
--- a/README.md
+++ b/README.md
@@ -111,11 +111,8 @@ current build process:
 3.  Loading all of the Debian and Ubuntu packages produced above into
     the staging instances of a set of APT repositories.
 
-4.  Uploading changes from the staging repositories to our public APT
-    repositories.
-
-5.  Generation of a [Homebrew][] formula and committing that formula to
-    the staging instance of a Homebrew "tap" (git repository), using a
+4.  Generation of a [Homebrew][] formula and committing that formula to
+    the staging instance of a Homebrew "tap" (git repository), using the
     tarball created during the Debian source package stage as the
     source package.  The Homebrew formula is source-only (no "bottled"
     binary packages): creating binary packages would not be
@@ -124,6 +121,9 @@ current build process:
     doesn't permit this unless we run our build farm on Apple
     hardware.
 
+5.  Uploading changes from the staging repositories to our public
+    repositories.
+
 In theory, it would also be possible to produce Windows binaries using
 the [MinGW][] cross-compilation environment, but Windows is sufficiently
 different from all other platforms that even minimal Windows support

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.