Maneage - Tasks: task #15732, Minor typos/language...
You are not allowed to post comments on this tracker with your current authentication level.
task #15732: Minor typos/language corrections/clarifications
Submitter: | Boud Roukema <boud> | ||
Submitted: | Mon 20 Jul 2020 05:55:51 PM UTC | ||
Should Start On: | Mon 20 Jul 2020 12:00:00 AM UTC | Should be Finished on: | Mon 20 Jul 2020 12:00:00 AM UTC |
Category: | None | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
Tue 21 Jul 2020 08:41:39 PM UTC, comment #4: |
Boud Roukema <boud>![]() |
Tue 21 Jul 2020 04:43:17 PM UTC, comment #3: Thanks Boud, good (and useful!) point ;-)! It is now in Maneage under Commit 2fadf4ba6f.
|
Mohammad Akhlaghi <makhlaghi>![]() |
Tue 21 Jul 2020 04:22:30 PM UTC, comment #2: Here's a one-line commit to clarify to the user how s/he might want to solve a failed checksum for downloads:
|
Boud Roukema <boud>![]() |
Mon 20 Jul 2020 09:42:04 PM UTC, comment #1: Thanks Boud, I agree, it would be good to have this task for small commits that would just crowd the bug/task lists!
|
Mohammad Akhlaghi <makhlaghi>![]() |
Mon 20 Jul 2020 05:55:51 PM UTC, original submission:
I propose that this be like on gnuastro(?) - a permanent task for posting pull requests for small minor commits.
|
Boud Roukema <boud>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
comment #3:
I see that my branch of maneage has already diverged a bit - in my case the '$$(pwd)' is necessary. :) A merge or commit proposal will have to be left to later...
I was mostly using the backtick because github and bitbucket use something like markdown, in which the backtick is useful for strings of code. That's not an ethical reason, it's a practical reason. Savannah uses a different form of markup, so in principle it's a good idea to switch here. Also, I see that codeberg, running gitea , does not seem to pass git commit comments through any sort of font convertor like markdown or rich markup.
Following https://www.gnu.org/prep/standards/html_node/Quote-Characters.html#Quote-Characters I'm happy to try either apostrophes or double quotes.
I included a full quote of your previous comment, but replaced '-verbatm-' by '-verbatim-' in order to properly close the verbatim section. It turned out that your verbatim section was kept secret from the html rendered version because of the typo... :)