From 5a2091381996586543b2218c27c40d879ca02551 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Sun, 2 Jan 2022 16:50:10 -1000 Subject: [PATCH] ;doc: RELEASING: formatting --- RELEASING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 1e4ae90de..71985d5c0 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -29,8 +29,8 @@ Tips for hledger release managers and maintainers. | *working copy, clone* | A local copy of a repository's files. Typically each developer has one or more of these, and can share changes easily with the official public repository. | | *branch* | Some VCS's, including Git, can store multiple branching lines of development within one repository. A working copy can be quickly switched to a different branch to show its content. | | | **hledger repos and branches** | -| *hledger repo* | The `hledger` git repository, containing the hledger software, reference manuals, and developer docs.
| -| *site repo* | The `hledger_website` git repository, containing most of the hledger website which appears at . Usually checked out under the hledger repo as `site/`.
| +| *hledger repo* | The `hledger` git repository, containing the hledger software, reference manuals, and developer docs. | +| *site repo* | The `hledger_website` git repository, containing most of the hledger website which appears at . Usually checked out under the hledger repo as `site/`. | | *release branch* | Branches named `MA.JOR-branch` in the hledger repo, eg `1.24-branch`. Releases are always made from a corresponding release branch (from 2022 on). | | *master* | The branch named `master` in the hledger repo; the main line of hledger development. Dev snapshots, and pull requests, can be made from here. | | | |