Typo in the developer's guide

[saraedum]

Should one really open a ticket for something like this?

where <repo-name> is the name of the repository you are using, and <format is “html”, “pdf”, [...]

---

Apply only attachment: trac_11816_typo.proper.patch to the Sage library.

Component: documentation

Author: Julian Rueth

Reviewer: Leif Leonhardy

Merged: sage-4.7.2.alpha3

Issue created by migration from https://trac.sagemath.org/ticket/11816

[saraedum]

fixes a typo in the developer's guide

[saraedum]

comment:1

Attachment: trac_11816_typo.patch.gz

[nexttime]

Replying to @saraedum:

Should one really open a ticket for something like this?

In principle yes, since otherwise they're likely to stay forever.

In this case, I'm pretty sure I've already corrected it in a not-yet-published version (a reviewer patch I have to provide for another ticket), but haven't found the time to finish it.

Once you start looking for typos, wrong formatting and inconsistencies (or meanwhile obsolete information), you're likely to not get to an end, unfortunately... ;-)

[nexttime]

Reviewer: Leif Leonhardy

[nexttime]

Merged: sage-4.7.2.alpha3

[nexttime]

Attachment: trac_11816_typo.proper.patch.gz

"Proper" Mercurial changeset replacement patch.

[nexttime]

comment:5

I've attached a *.proper.patch, which is identical except that I removed the "garbage" before "# HG changeset patch", i.e., I deleted the first line "exporting patch:", since Jeroen's current merger rejects such patches.

For now, please make sure all your patches start with "# HG changeset patch", i.e., have it on the first line without any preceding messages or whatever.

I've relaxed that in my version of the merger, but Jeroen and maybe others are likely to use his more restrictive one.