emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: ox-publish: Some starting problems
Date: Wed, 9 Mar 2022 22:57:28 +0700	[thread overview]
Message-ID: <t0aip9$ifc$1@ciao.gmane.io> (raw)
In-Reply-To: <109f0b7f9d53af31a5e1ab00c7384c58@posteo.de>

On 09/03/2022 16:41, c.buhtz@posteo.jp wrote:
> Should I then open a bug report? Do I understand 
> https://orgmode.org/worg/org-issues.html correct that there is no 
> "usual" bug tracker but just he mailing list where I have to post bugs?

There is a kind of dashboard at https://updates.orgmode.org Someone need 
to confirm the bug report before it will appear there.

Accordingly to https://orgmode.org/org.html#Feedback
you may use
    M-x org-submit-bug-report <RET>
or just to send description of the problem to this list.

There is a subpackage for Org Mode at https://debbugs.gnu.org, but the 
message will be anyway redirected to this mail list. Bugs reported 
against Emacs instead of Org Mode have greater chance to remain 
unnoticed for some period of time. Answers sent to the mail list 
directly instead of the bug email address will not appear in debbugs 
archives. Notice the following as well:

Bastien. Re: issue tracker? Mon, 01 Jun 2020 16:36:59 +0200
 > I'd like to keep this mailing list as the central place to discuss
 > everything about Org, including bug reports.

  reply	other threads:[~2022-03-09 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  8:55 ox-publish: Some starting problems c.buhtz
2022-03-09  9:41 ` c.buhtz
2022-03-09 15:57   ` Max Nikulin [this message]
2022-03-09 15:32 ` Max Nikulin
2022-03-09 16:39   ` c.buhtz
2022-03-11 19:21     ` chris
2022-03-15 13:04     ` Max Nikulin
2022-03-10 21:49 ` Nick Dokos

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:

  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='t0aip9$ifc$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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