all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Thuna <thuna.cing@gmail.com>
Cc: 61546@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#61546: [PATCH] Fix some org functionality breaking upon changing `calendar-buffer'
Date: Thu, 16 Feb 2023 09:57:09 +0000	[thread overview]
Message-ID: <87y1oy2aru.fsf@localhost> (raw)
In-Reply-To: <87mt5e2bsi.fsf@gmail.com>

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

>> In general, it's better to send patches for org-mode to the org-mode
>> mailing list.
>
> Right, sorry, I split this off of 61547 and forgot to send it to the
> org-mode mailing list.  Should I do it now or is it fine here also?

I happen to see this email.

The patch looks fine, even if the other patch is not merged.
It is also compatible with Emacs 26.

However, I need to know if you have FSF copyright assignment. If not,
you will need to add TINYCHANGE cookie to the commit message. See
https://orgmode.org/worg/org-contribute.html#first-patch

-- 
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  9:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  6:01 bug#61546: [PATCH] Fix some org functionality breaking upon changing `calendar-buffer' Thuna
2023-02-16  9:24 ` Stefan Kangas
2023-02-16  9:35   ` Thuna
2023-02-16  9:57     ` Ihor Radchenko [this message]
2023-02-16 10:02       ` Thuna
2023-02-16 10:17         ` Ihor Radchenko
2023-02-28  9:28           ` Bastien Guerry
2023-02-28  9:28           ` Bastien Guerry
2023-02-16 10:17         ` Ihor Radchenko
2023-05-02 11:38 ` Ihor Radchenko
2023-05-02 18:04   ` Eli Zaretskii

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

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

  git send-email \
    --in-reply-to=87y1oy2aru.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=61546@debbugs.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.