From: Ihor Radchenko <yantar92@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, emacs-orgmode@gnu.org
Subject: Re: Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)]
Date: Sat, 02 Oct 2021 13:25:19 +0800 [thread overview]
Message-ID: <874ka0yp4w.fsf@localhost> (raw)
In-Reply-To: <87v92gnhsv.fsf@bzg.fr>
Bastien <bzg@gnu.org> writes:
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> Should I also merge main with bugfix every time?
>
> You should merge bugfix into main, yes (but not main into bugfix.)
Thanks for the clarification. It indeed makes sense, but I was not sure
if merging too frequently is ok or not.
Best,
Ihor
next prev parent reply other threads:[~2021-10-02 5:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 11:46 Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Dr. Arne Babenhauserheide
2021-10-01 9:56 ` Ihor Radchenko
2021-10-02 4:30 ` Bastien
2021-10-02 4:52 ` Ihor Radchenko
2021-10-02 4:59 ` Bastien
2021-10-02 5:25 ` Ihor Radchenko [this message]
2021-10-25 12:57 ` Ihor Radchenko
2021-10-25 17:33 ` Bastien
2021-10-26 6:44 ` Greg Minshall
2021-10-26 6:56 ` Bastien
2021-10-26 7:33 ` Greg Minshall
2021-10-26 17:11 ` Max Nikulin
2021-10-27 7:08 ` (Reopened) Bug: font-lock error with - in code-mode Ihor Radchenko
2021-10-27 11:50 ` Cancel "yes" entry on updates.orgmode.org (was: Re: Bug: font-lock error with - in code-mode) Max Nikulin
2021-10-27 16:51 ` Max Nikulin
2021-10-02 5:07 ` Bug: font-lock error with - in code-mode [9.4.6 (9.4.6-gab9f2a @ /gnu/store/2pny4z6mbi2aybgzzxz0yrzkds7hbpmq-emacs-org-9.4.6/share/emacs/site-lisp/org-9.4.6/)] Ihor Radchenko
2021-10-28 14:03 ` Bug: font-lock error with - in code-mode (reopened) Max Nikulin
2021-10-28 14:16 ` Ihor Radchenko
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=874ka0yp4w.fsf@localhost \
--to=yantar92@gmail.com \
--cc=arne_bab@web.de \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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.