From: Eli Zaretskii <eliz@gnu.org>
To: jostein@kjonigsen.net
Cc: 59602@debbugs.gnu.org, theo@thornhill.no, stefankangas@gmail.com
Subject: bug#59602: 29.0.50; csharp-mode should either be a package, or compat code could be removed
Date: Sun, 27 Nov 2022 08:04:07 +0200 [thread overview]
Message-ID: <83pmd9q6g8.fsf@gnu.org> (raw)
In-Reply-To: <495b9dec-013f-5248-8a57-5539f16575d7@secure.kjonigsen.net> (message from Jostein Kjønigsen on Sat, 26 Nov 2022 21:58:35 +0100)
> Date: Sat, 26 Nov 2022 21:58:35 +0100
> From: Jostein Kjønigsen <jostein@secure.kjonigsen.net>
>
> While don't expect that providing for unlimited git-access out of the blue probably is how new major-modes
> are taken in, I'm also not sure what the "normal" procedure is in cases like this.
The "normal" procedure is to keep posting patches for review until you feel
you've been doing that long enough, and managed to get to the state where
your patches get only minor review comments, especially about coding and
documentation conventions. Then request write access.
> Are there someone particular we are recommended to CC in our emails to make sure the patches get
> picked up efficiently? And what if it's not a registered "bug" yet, but just an improvement? Should we send it
> to emacs-devel instead?
It is always best to use report-emacs-bug for sending patches, even if it
isn't a bug. debbugs is our issue tracker, not just bug tracker.
emacs-devel is for discussing ideas and asking questions (you can also post
diffs to better explain what you mean or if the question is about a
particular code).
TIA
next prev parent reply other threads:[~2022-11-27 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 8:14 bug#59602: 29.0.50; csharp-mode should either be a package, or compat code could be removed Stefan Kangas
2022-11-26 19:12 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-26 20:58 ` Jostein Kjønigsen
2022-11-27 6:04 ` Eli Zaretskii [this message]
2022-11-27 9:38 ` Stefan Kangas
2022-11-27 9:58 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83pmd9q6g8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59602@debbugs.gnu.org \
--cc=jostein@kjonigsen.net \
--cc=stefankangas@gmail.com \
--cc=theo@thornhill.no \
/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.