diff options
| author | Guido Günther <agx@sigxcpu.org> | 2017-12-16 16:48:55 +0100 |
|---|---|---|
| committer | Guido Günther <agx@sigxcpu.org> | 2017-12-16 16:48:55 +0100 |
| commit | 4312e54b6ed154f4149ddcfd1b88a40cc1b4caad (patch) | |
| tree | a860132a8484a113923be89c9c5bc1ec9b051b96 /docs | |
| parent | d9a5319ae466f71397a265df10704a37104cbdec (diff) | |
docs: Add ids to all sections
so we get nicer link names
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/chapters/import.xml | 6 | ||||
| -rw-r--r-- | docs/chapters/releases.xml | 8 |
2 files changed, 7 insertions, 7 deletions
diff --git a/docs/chapters/import.xml b/docs/chapters/import.xml index df75ce58..443255d7 100644 --- a/docs/chapters/import.xml +++ b/docs/chapters/import.xml @@ -109,7 +109,7 @@ by version number. your message to get the imported upstream version). </para> - <sect2> + <sect2 id="gbp.import.error.recovery"> <title>Recovering from errors</title> <para>In case of an error &gbp-import-orig; will by default rollback (undo) all changes it has done to the repository so far: @@ -145,7 +145,7 @@ by version number. If the &git; repository wasn't created with &gbp-import-dsc;, you have to tell &gbp-buildpackage; and friends where to find the upstream sources. </para> - <sect2> + <sect2 id="gbp.import.upstream.on.branch"> <title>Upstream sources on a branch</title> <para> If the upstream sources are already on a separate branch, things are pretty @@ -168,7 +168,7 @@ EOF merged to the <option>debian-branch</option>. </para> </sect2> - <sect2> + <sect2 id="gbp.import.upstream.not.on.branch"> <title>Upstream sources not on a branch</title> <para> If you don't have an upstream branch but started your repository with only diff --git a/docs/chapters/releases.xml b/docs/chapters/releases.xml index 3fc8ec02..50aa87cb 100644 --- a/docs/chapters/releases.xml +++ b/docs/chapters/releases.xml @@ -20,9 +20,9 @@ commits. Invocations of &dch; and &gbp-dch; can be mixed. </para> - <sect1> + <sect1 id="gbp.maintaining.changelog"> <title>Maintaining <filename>debian/changelog</filename></title> - <sect2> + <sect2 id="gbp.changelog.release"> <title>Creating &changelog; just before the release</title> <para> The simplest way is doing all the changes to the @@ -39,7 +39,7 @@ finally spawns an editor for final changelog editing. </para> </sect2> - <sect2> + <sect2 id="gbp.incremental.changelog"> <title>Incrementally filling &changelog;</title> <para> You can run &gbp-dch; without any options to make it add all @@ -60,7 +60,7 @@ </sect2> </sect1> - <sect1> + <sect1 id="gbp.snapshots"> <title>Creating snapshots with increasing version numbers</title> <para> The downside of the above methods is that you either have the |