From: Ihor Radchenko <yantar92@posteo.net>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: TEC <orgmode@tec.tecosaur.net>, Org mailing list <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] [BUG] Support attr_html in source code and fixed-width blocks
Date: Mon, 22 Jul 2024 19:49:20 +0000 [thread overview]
Message-ID: <874j8hmclb.fsf@localhost> (raw)
In-Reply-To: <878qxt2paa.fsf@gmail.com>
Suhail Singh <suhailsingh247@gmail.com> writes:
> Given that I already have some contributions in Org mode and I don't, at
> present, intend to do the copyright assignment to FSF, could you please
> confirm:
>
> 1. How many lines worth of changes I can still introduce without going
> over the limit?
I do not see any commits under "suhailsingh247@gmail.com" or under
"Suhail Singh".
Commits under similar names are:
Suhail 96eb9f0b4 * piem/s/org-lint-add-function-to-removeJun6 org-lint: Add function to remove checker(s)
Suhail Shergill 3b2abfce7 * bugfix: fix `org-babel-execute-src-block' on remote hosts
Suhail Shergill 28582bfa0 * org-html.el: Make footnotes unique to an entry
Utkarsh Singh e62618508 * org-table.el: Fix usage of user-error
Utkarsh Singh 7c99d1555 * org-table.el: Allow to import files with no .txt, .tsv or .csv
I assume that 96eb9f0b4 is yours.
It has 9 LOC.
~6LOC remaining until aproximate 15LOC limit we can accept without
copyright assignment.
> 2. When implementing such refactoring changes, which lines are counted?
More or less all lines, except things like blank lines, query replace,
or copy-pasted code (or, in other words, trivial changes)
> From a feasibility perspective, I suspect it might be better for you (or
> someone else who's signed the FSF copyright assignment paperwork) to
> take on the work of applying changes that are similar in spirit to the
> patch.
Maybe, but that's a subject of my time and priorities.
This particular bug/feature request will not be high in the priority
list. Unless we get more users jumping to this thread and asking for
#+ATTR_HTML support.
--
Ihor Radchenko // yantar92,
Org mode contributor,
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>
next prev parent reply other threads:[~2024-07-22 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 2:55 [PATCH] [BUG] Support attr_html in source code and fixed-width blocks Suhail Singh
2024-06-18 15:33 ` Ihor Radchenko
2024-07-19 15:28 ` Suhail Singh
2024-07-22 13:49 ` Ihor Radchenko
2024-07-22 17:11 ` Suhail Singh
2024-07-22 18:13 ` Ihor Radchenko
2024-07-22 18:45 ` Suhail Singh
2024-07-22 19:10 ` Ihor Radchenko
2024-07-22 19:35 ` Suhail Singh
2024-07-22 19:49 ` Ihor Radchenko [this message]
2024-07-22 20:05 ` Suhail Singh
2024-09-02 13:03 ` Suhail Singh
2024-09-07 18:10 ` Ihor Radchenko
2024-09-07 19:45 ` Suhail Singh
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=874j8hmclb.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--cc=suhailsingh247@gmail.com \
/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).