brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject brooklyn-docs git commit: minor tweak to submodule instructions
Date Tue, 02 Feb 2016 01:42:41 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 4e4aed4b5 -> eb38d4625

minor tweak to submodule instructions


Branch: refs/heads/master
Commit: eb38d462513c3b5a7cfaa912e240ae3fc24ead68
Parents: 4e4aed4
Author: Alex Heneveld <>
Authored: Tue Feb 2 01:41:31 2016 +0000
Committer: Alex Heneveld <>
Committed: Tue Feb 2 01:41:31 2016 +0000

 guide/dev/code/ | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/guide/dev/code/ b/guide/dev/code/
index a589edf..e72ab20 100644
--- a/guide/dev/code/
+++ b/guide/dev/code/
@@ -27,9 +27,7 @@ Some options which may be useful:
 * Use `--depth 1` with `git clone` to skip the history (much faster but your `git log` will
be incomplete)
 * Use `-DskipTests` with `mvn` to skip tests (again much faster but it won't catch failures)
-* Drop `--recursive` on the `git clone` and set up some submodules manually 
-  (e.g. with `git submodule init && git submodule update --remote [module]`) 
-  or avoid submodules, following the directions below
+* See below if you don't want to use submodules
 Thereafter to update the code in submodules, we strongly recommend doing this:
@@ -39,7 +37,8 @@ This merges the latest upstream changes into the current branch of each
 giving nice errors on conflicts.
 It's fine also to do branching and pulling in each submodule,
 but running `update` without these parameters can cause chaos!
-This chaos -- and a `git sup` alias for this command -- are described in the [submodules](submodules.html)
+The [submodules](submodules.html) page will elaborate on potential chaos and pitfalls,
+and it provides instructions for setting up an alias `git sup` for this command.
 ### If You Can't Stand Submodules

View raw message