From: Bastien <email@example.com> To: Timothy <firstname.lastname@example.org> Cc: org-mode-email <email@example.com> Subject: Re: [PATCH] Date: Wed, 28 Apr 2021 08:36:20 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Timothy's message of "Wed, 28 Apr 2021 11:53:24 +0800") Hi Timothy, Timothy <firstname.lastname@example.org> writes: > Bastien <email@example.com> writes: > >> Feel free to install changes when they have reached consensus, >> or to ask for decisions when not. > > Thanks for the reply Bastien, would you mind elaborating on this a bit > more? I'm comfortable with the idea of what I can do with org-plot.el as > the maintainer (directly push, but field patches to the ML for > non-trivial changes), but as a non-core-contributor I didn't think I > could push my own patches for other things. Regular contributors can commit patches themselves whenever the maintainers say so. > Also, with the batch of patches I sent a plea about recently, how would > you recommend I proceed with that? There doesn't seem to be any > consensus or decision despite prompting. Perhaps that's because such plea contains too many different issues. I will reply there. Thanks, -- Bastien
next prev parent reply other threads:[~2021-04-28 6:36 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-20 10:46 [PATCH] TEC 2021-01-20 11:00 ` [PATCH] tweaks to ox-html style TEC 2021-02-12 6:16 ` Kyle Meyer 2021-02-12 16:57 ` Jens Lechtenboerger 2021-02-12 17:08 ` Jens Lechtenboerger 2021-02-12 18:22 ` Timothy 2021-02-13 14:43 ` Jens Lechtenboerger 2021-02-12 18:16 ` Timothy 2021-02-12 21:46 ` Tim Cross 2021-02-13 9:28 ` Eric S Fraga 2021-02-13 13:32 ` Christian Moe 2021-02-14 4:36 ` Timothy 2021-04-28 3:38 ` [PATCH] Bastien 2021-04-28 3:53 ` [PATCH] Timothy 2021-04-28 6:36 ` Bastien [this message] 2021-04-28 6:33 ` [PATCH] Bastien -- strict thread matches above, loose matches on Subject: below -- 2021-09-26 11:51 [PATCH] Timothy 2021-09-26 12:01 ` [PATCH] Timothy 2021-09-26 12:14 ` [PATCH] Timothy 2021-09-27 8:19 ` [PATCH] Bastien 2021-09-27 10:35 ` [PATCH] Timothy 2021-09-27 11:45 ` [PATCH] Bastien 2021-09-27 12:20 ` [PATCH] Timothy 2021-09-27 12:31 ` [PATCH] Bastien 2021-09-27 15:26 ` [PATCH] Bastien 2021-09-27 15:36 ` [PATCH] Timothy 2021-09-27 17:44 ` [PATCH] Bastien 2021-09-27 17:52 ` [PATCH] Timothy 2021-09-27 19:45 ` [PATCH] Bastien 2021-09-28 15:31 ` [PATCH] Bastien Guerry 2021-09-28 15:50 ` [PATCH] Timothy 2011-07-13 14:13 [PATCH] Evgeny Boykov 2011-07-16 17:10 ` [PATCH] Bastien
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 List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH]' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).