----- Original Message -----
From: "Ihor Radchenko" <yanta...@posteo.net>
To: "Raoul Comninos" <revr...@mweb.co.za>
Cc: emacs-orgmode@gnu.org
Sent: Sunday, May 4, 2025 9:25:20 AM
Subject: Re: [PATCH] org-tutorials: Add Org-mode video tutorials by Raoul 
Comninos

Raoul Comninos <revr...@mweb.co.za> writes:

> Please find attached a patch that adds a link to my 8-part video
> tutorial series
> on Org-mode fundamentals to the tutorials index page.

Applied, onto master.
https://git.sr.ht/~bzg/worg/commit/bbea0983

> * org-tutorials/index.org (General Introductions to Org-mode): Add link
> to 8-part video tutorial series covering Org-mode fundamentals

> .... including
> structures, motions, editing, sparse trees, lists, drawers, footnotes,
> hyperlinks, and rich text formatting.

This second part of the commit message is ok, but probably redundant.
Simply because commit message describes changes made, not the contents.
Only people interested in *editing* WORG may read commit messages. So,
they should generally explain what and why was changed, not the details
that should normally go into the .org page itself.

> +# I feel the titles give the User precise information and shows they
> real world working useful things, but it's bulky like this. Please
> let's talk about if/how to show this sub-list... :)

Note this comment. It will not appear on the actual WORG page, but hints
on one of the improvements you can make in WORG.  At least, it may be
worth it to add this comment to the todo file.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Thank you Ihor for applying the patch. 

Regarding the comment about sub-lists, that was already present in the file 
before my changes—I only added my video tutorial link underneath it. 

I appreciate your guidance about commit messages. I will keep in mind the 
difference between focusing on what has changed rather than content details in 
the future.

Reply via email to