emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Rohit Patnaik <quanticle@quanticle.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Feature Request] Create an org-md-toplevel-hlevel variable to allow users to set the level of top level headings in markdown export
Date: Fri, 26 Aug 2022 21:07:16 +0800	[thread overview]
Message-ID: <87fshjxiez.fsf@localhost> (raw)
In-Reply-To: <1335376b-0eeb-472c-8b8d-988eb0bdd04b@www.fastmail.com>

"Rohit Patnaik" <quanticle@quanticle.net> writes:

> I've added the entry in the NEWS file, added the entry for the new
> variable to section 14.1.5 of the manual, updated the docstring to
> have double space periods, and updated the commit message to follow
> the changelog style described on
> https://orgmode.org/worg/org-contribute.html#comment-messages.

Applied onto main via b7f4afe86 with amendments.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=b7f4afe86c36c36a751cb9dd31daa69051eec506

I have modified the commit message adding " " between sentences and
adding "." after sentences. Also, I added TINYCHANGE cookie as you do
not appear to have a copyright assignment.

Finally, I rewrote the variable docstring in order to make it more clear
(hopefully). I also refilled the docstring to 80 chars width.

Thanks for your contribution!

Best,
Ihor


  parent reply	other threads:[~2022-08-26 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 20:20 [Feature Request] Create an org-md-toplevel-hlevel variable to allow users to set the level of top level headings in markdown export Rohit Patnaik
2022-08-20  7:49 ` Ihor Radchenko
2022-08-21 11:07   ` Rohit Patnaik
2022-08-21 14:26     ` Max Nikulin
     [not found]       ` <47b3902e-cc80-4317-a761-9301abd50b3c@www.fastmail.com>
2022-08-22 12:03         ` Max Nikulin
2022-08-22  2:59     ` Ihor Radchenko
     [not found]       ` <1335376b-0eeb-472c-8b8d-988eb0bdd04b@www.fastmail.com>
2022-08-26 13:07         ` Ihor Radchenko [this message]
2022-08-26 15:34           ` Rohit Patnaik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fshjxiez.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=quanticle@quanticle.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).