You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@turbine.apache.org by gk...@apache.org on 2023/03/09 11:20:14 UTC

[turbine-build] branch master updated: fix typos in README*, reference readmes, rename site readme

This is an automated email from the ASF dual-hosted git repository.

gk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/turbine-build.git


The following commit(s) were added to refs/heads/master by this push:
     new c25f6f7  fix typos in README*, reference readmes, rename site readme
c25f6f7 is described below

commit c25f6f767f64e586f2db8fe6a519dc315d9b18c3
Author: Georg Kallidis <gk...@apache.org>
AuthorDate: Thu Mar 9 12:19:00 2023 +0100

    fix typos in README*, reference readmes, rename site readme
---
 README.md                                                      | 6 +++++-
 README_TECHNICAL_SITE_STRUCTURE.md => README_SITE_STRUCTURE.md | 2 +-
 README_TECHNICAL_GITMODULES.md                                 | 4 ++--
 3 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 08a5c26..6306921 100644
--- a/README.md
+++ b/README.md
@@ -27,6 +27,8 @@ https://maven.apache.org/guides/getting-started/
 
 Turbine Build does use (Git Submodules)[https://git-scm.com/book/en/v2/Git-Tools-Submodules].
 
+Find more detailed information (here)[README_TECHNICAL_GITMODULES.md].
+
 You could use git to checkout current trunk:
 
      git clone --recurse-submodules https://github.com/apache/turbine-build.git 
@@ -260,7 +262,9 @@ If no sha512 files are in the target folder, check local repo.
 
 ## Git Checkout <tagged release version> source. Generate and Publish Site
 
-### Description of the process using asf-site branch using GIT commands
+Find an overview about the technical structure of the sites (here)[README_SITE_STRUCTURE.md].
+
+### Short description of the process using asf-site branch using GIT commands
 
 Hint: If checking out the branch asf-site you find an .asf.yaml file, where the exact configuration is found, what happens after site generation.
 
diff --git a/README_TECHNICAL_SITE_STRUCTURE.md b/README_SITE_STRUCTURE.md
similarity index 97%
rename from README_TECHNICAL_SITE_STRUCTURE.md
rename to README_SITE_STRUCTURE.md
index fe0a816..a2c3b0d 100644
--- a/README_TECHNICAL_SITE_STRUCTURE.md
+++ b/README_SITE_STRUCTURE.md
@@ -68,7 +68,7 @@ After the new site is deployed, change subdir to the next version
     subdir: turbine/development/turbine-5-2
 
 After this Jenkinsfile could be used to publish the site in [Apache Build](https://builds.apache.org/).
-(WORK IN PROGRESS this has to tested yet).
+(WORK IN PROGRESS this has to tested more, but seems to be working).
 
 
 ## License
diff --git a/README_TECHNICAL_GITMODULES.md b/README_TECHNICAL_GITMODULES.md
index 2f6c670..1470169 100644
--- a/README_TECHNICAL_GITMODULES.md
+++ b/README_TECHNICAL_GITMODULES.md
@@ -15,9 +15,9 @@ You could use git to checkout current trunk:
 
      git clone https://gitbox.apache.org/repos/asf/turbine-build.git 
      
-N.B. The submodules are included with a relative URL. If you are cloning with https + Github  and you want later psuh you have to switsch either to ush) or the SSH-URL or fetching from gitbox (recommended).
+N.B. The submodules are included with a relative URL. If you are cloning with https + Github  and you want later push you have to switch either to the SSH-URL (ssh://git@github.com/) or fetching from gitbox (recommended) using your Apache credentials.
 
-If you want later update the remote URLS you could use sync command to achieve this:
+If you want later update the remote URLS you could use the sync command to achieve this:
 
     git submodule sync