emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Thuna <thuna.cing@gmail.com>, Bastien <bzg@gnu.org>
Cc: Stefan Kangas <stefankangas@gmail.com>,
	61546@debbugs.gnu.org, emacs-orgmode@gnu.org
Subject: Re: bug#61546: [PATCH] Fix some org functionality breaking upon changing `calendar-buffer'
Date: Thu, 16 Feb 2023 10:17:01 +0000	[thread overview]
Message-ID: <87v8k13of6.fsf@localhost> (raw)
In-Reply-To: <87k00i2aiy.fsf@gmail.com>

Thuna <thuna.cing@gmail.com> writes:

>> If not, you will need to add TINYCHANGE cookie to the commit
>> message. See https://orgmode.org/worg/org-contribute.html#first-patch
> That is a bit of an issue.  Do org contributions and emacs contributions
> count towards the same 15 LoC limit?  If so, I have already exhausted
> mine, so TINYCHANGE won't work.

AFAIK, we count separately. Org mode is a separate project, despite
being distributed together with Emacs. At least, we usually only
consider LOCs contributed to Org.

Let me CC Bastien (the Org maintainer) to clarify.

-- 
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>


       reply	other threads:[~2023-02-16 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r0uq2los.fsf@gmail.com>
     [not found] ` <CADwFkmkHG-pKhjoyPrZOrYktrjhFwQG+0DhP4m4jprL2ruR7_g@mail.gmail.com>
     [not found]   ` <87mt5e2bsi.fsf@gmail.com>
     [not found]     ` <87y1oy2aru.fsf@localhost>
     [not found]       ` <87k00i2aiy.fsf@gmail.com>
2023-02-16 10:17         ` Ihor Radchenko [this message]
2023-02-28  9:28           ` bug#61546: [PATCH] Fix some org functionality breaking upon changing `calendar-buffer' Bastien Guerry

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=87v8k13of6.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=61546@debbugs.gnu.org \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=thuna.cing@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).