From: Jack Kamm <firstname.lastname@example.org>
To: Bastien <email@example.com>
Cc: Christian Vanderwall <firstname.lastname@example.org>, email@example.com
Subject: Re: [PATCH] ob-python.el: Fix issue with sessions on remote machines
Date: Sat, 05 Sep 2020 07:39:40 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> - A local maintainer is expected to reply to requests and bug reports
> regarding the local functionalities he oversees.
> - A local maintainer can commit changes directly to the file(s) he
> maintains (either submitted changes or his own).
> - Core maintainers have the final word on any change in any file (so
> in case of a disagreement with a local maintainer, core maintainers
> have priority.)
> In general, I would like to encourage "optimistic merging" from more
> "local" maintainers.
> Does that sound right? When in doubt, always discuss changes first.
I agree with this policy, and am more or less following it already,
though it's good to be explicit.
I'm keeping an eye out for Python-related mail, but if it looks like
I've missed one, add me to the TO or CC field to ensure it lands in my
I appreciate the freedom to make changes to ob-python, but of course
defer to you, Nicolas, and Kyle, and seek out guidance when unsure.
next prev parent reply other threads:[~2020-09-05 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 18:47 [PATCH] ob-python.el: Fix issue with sessions on remote machines Christian Vanderwall
2020-08-18 14:21 ` Jack Kamm
2020-08-21 1:37 ` Jack Kamm
2020-09-04 9:55 ` Bastien
2020-09-05 1:08 ` Jack Kamm
2020-09-05 8:15 ` Bastien
2020-09-05 14:39 ` Jack Kamm [this message]
2020-09-05 14:48 ` Bastien
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 \
* 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).