You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by wa...@apache.org on 2021/06/28 21:30:52 UTC
[openoffice-project] branch preview/refresh updated: fixup headings
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch preview/refresh
in repository https://gitbox.apache.org/repos/asf/openoffice-project.git
The following commit(s) were added to refs/heads/preview/refresh by this push:
new f565bbc fixup headings
f565bbc is described below
commit f565bbcd6848559c8eedf2e52bb0c74080da491d
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Mon Jun 28 14:28:57 2021 -0700
fixup headings
---
content/license.md | 2 +-
content/mailing-lists.md | 4 ++--
content/orientation/intro-development.md | 4 ++--
content/pmc-faqs.md | 2 +-
content/svn-basics.md | 22 +++++++++++-----------
5 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/content/license.md b/content/license.md
index 74c30b0..a7761e5 100644
--- a/content/license.md
+++ b/content/license.md
@@ -171,7 +171,7 @@ liability.
END OF TERMS AND CONDITIONS
-# APPENDIX: How to apply the Apache License to your work # {#apply}
+# APPENDIX: How to apply the Apache License to your work {#apply}
To apply the Apache License to your work, attach the following boilerplate
notice, with the fields enclosed by brackets "[]" replaced with your own
diff --git a/content/mailing-lists.md b/content/mailing-lists.md
index 6abc88d..b8efb11 100644
--- a/content/mailing-lists.md
+++ b/content/mailing-lists.md
@@ -38,7 +38,7 @@ Every OpenOffice mailing list has a list address, of the form:
*xyz*@openoffice.apache.org, where you **replace "*xyz*" with the actual list name**,
such as "dev" or "qa" or "marketing".
-### Basic Operations ###
+### Basic Operations
There are three basic operations you should know about:
@@ -229,7 +229,7 @@ people and tries to help to find the right part. This is a low traffic list.
- Apache Archives: [current][87]
- Third-party Archives: [Mail Archive][81]
-##<a id="native-lang-lists"></a> Native Language (non-English) Mailing Lists
+## Native Language (non-English) Mailing Lists {#native-lang-lists}
The project has several mailing lists for discussion about OpenOffice in native
(non-English) languages.
diff --git a/content/orientation/intro-development.md b/content/orientation/intro-development.md
index 1852ce9..e4248fb 100644
--- a/content/orientation/intro-development.md
+++ b/content/orientation/intro-development.md
@@ -1,7 +1,7 @@
Title: Introduction to Development
Notice: http://www.apache.org/licenses/LICENSE-2.0
-##Introduction
+## Introduction
In this orientation module you will learn how to get started programming OpenOffice.
@@ -15,7 +15,7 @@ Note: In parallel with the Dev-specific items on this page, you may want to also
Now with the introductions out of the way, let's get started!
-##OpenOffice Development: Good, the Bad and the Ugly
+## OpenOffice Development: Good, the Bad and the Ugly
Let's be honest. The size, age and complexity of OpenOffice's C++ codebase makes coding a challenge. This is not a trivial codebase to learn. But if you like a good challenge then you'll love this project! There are tasks suitable for programmers with a range of programming experience, and we have many veteran OpenOffice hackers in the project who are happy to answer your questions.
diff --git a/content/pmc-faqs.md b/content/pmc-faqs.md
index 1a86f6a..12cd605 100644
--- a/content/pmc-faqs.md
+++ b/content/pmc-faqs.md
@@ -14,7 +14,7 @@ is responsible for the project and decides what to do and which direction to go.
<br> ([see here for a list of PMC members][1])
-# Who is the Admin/Moderator/Owner for X? # {#moderator}
+# Who is the Admin/Moderator/Owner for X? {#moderator}
Although Apache projects have few formal roles, there are some technical subsystems
which have admin or similar roles filled by project volunteers. If you have a question
diff --git a/content/svn-basics.md b/content/svn-basics.md
index 30132d2..d9147f3 100644
--- a/content/svn-basics.md
+++ b/content/svn-basics.md
@@ -18,13 +18,13 @@ This page gives instructions on performing basic development tasks using the Sub
* [Merging changes to a branch](#merging_changes)
* [Further Information](#further_information)
-## <a id="overview"></a>Overview
+## Overview {#overview}
You begin using Subversion by copying a directory from a remote repository to a local directory on your file system. This is known as a checkout of a working copy.
Subversion uses a copy-modify-merge model meaning that you can add and edit files and directories in your working copy like any other files on your system, but you should use subversion commands for everything else such as `svn copy` and `svn move` instead of the operating system commands.
-## <a id="sub-commands_and_abbreviations"></a>Sub-commands and Abbreviations
+## Sub-commands and Abbreviations {#sub-commands_and_abbreviations}
Subversion commands can be run from a command shell such as Bash on Linux. The subversion client command is `svn` followed by optional sub-commands, options, and arguments.
@@ -53,7 +53,7 @@ The following is only a partial list of sub-commands relating to this instructio
* `status` - Print the status of working copy files and directories
* `update` - Bring changes from the repository into your working copy
-## <a id="client_configuration"></a>Client Configuration
+## Client Configuration {#client_configuration}
Committers need to [configure their Subversion client][6] to handle the differences in line endings of text files on different operating systems.
@@ -61,7 +61,7 @@ There are instances where Subversion may need to open an editor. You need to hav
$ export EDITOR=/usr/bin/vim
-## <a id="repository_layout"></a>Repository Layout
+## Repository Layout {#repository_layout}
The AOO repository layout uses the following top-level directories `branches`, `site`, `tags`, and `trunk`.
@@ -87,7 +87,7 @@ From the parent directory of where you want the working copy. In this example th
"A" indicates file or directory is "Added" to working copy
-## <a id="basic_work_cycle"></a>Basic Work Cycle
+## Basic Work Cycle {#basic_work_cycle}
* Update your working copy - For this you use the `svn update` command
* Make changes - For this you may edit files in an editor, or use the `svn add`, `svn delete`, `svn copy`, `svn-move` commands
@@ -201,7 +201,7 @@ If you choose `e`, Subversion will launch an editor with both sets of changes in
"G" indicates "merGed"
-## <a id="committing_changes"></a>Committing Changes
+## Committing Changes {#committing_changes}
Only Committers can commit directly to the repository. The following example shows using your Apache ID and password.
@@ -218,7 +218,7 @@ you don't specify, SVN will commit **all** your changes.
For further information see the [Basic Work Cycle][8] page from [Subversion Book][2].
-## <a id="commit_message"></a>Commit Message
+## Commit Message {#commit_message}
The examples in the previous sections use a simple commit message with the "-m" option.
This is fine for some quick testing or for large bulk commits of code that you wrote.
@@ -244,7 +244,7 @@ Use of the special fields will enable processing by scripts like the
contributors.
-## <a id="committing_changes_by_others"></a>Committing Changes By Others
+## Committing Changes By Others {#committing_changes_by_others}
See the [Applying Patches][9] section of the Committer FAQ page. Please use the special fields
described in the previous Commit Message section to commit changes supplied by others.
@@ -263,7 +263,7 @@ An alternative way is the following command. It adds a new line with "\n":
John Doe <john.doe.at.null.org>\nSubmitted by: John Doe /
<john.doe.at.null.org>' test-file.txt
-## <a id="creating_and_submitting_patches"></a>Creating and Submitting Patches
+## Creating and Submitting Patches {#creating_and_submitting_patches}
See the [Sending in Patches][10] section on the Contributors Tech Guide page.
@@ -271,7 +271,7 @@ Create the patch file from `svn diff` where `your-patch-name.patch` is the full
svn diff > your-patch-name.patch
-## <a id="merging_changes"></a>Merging changes to a branch
+## Merging changes to a branch {#merging_changes}
New development is done in the "trunk", development area, of the tree. Stable, release branches, are specifically named and can be found
in the [branches](http://svn.apache.org/viewvc/openoffice/branches/) area of the openoffice svn tree. With few exceptions you do **NOT** do direct commits to the stable, release,
@@ -331,7 +331,7 @@ and commit from the aoo-update directory:
Transmitting file data ..
Committed revision 1347377.
-## <a id="further_information"></a>Further Information
+## Further Information {#further_information}
For more information see: