From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug#48548: 28.0.50; Some process attributes on macOS are missing
Date: Fri, 21 May 2021 15:30:38 +0300 [thread overview]
Message-ID: <m2pmxk46c1.fsf@fastmail.fm> (raw)
In-Reply-To: <83wnrsmlej.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 May 2021 13:27:48 +0300")
On 21/05/2021 13:27 +0300, Eli Zaretskii wrote:
>> From: Filipp Gunbin <fgunbin@fastmail.fm>
>> Date: Fri, 21 May 2021 12:50:50 +0300
>> Cc: bug-gnu-emacs@gnu.org, emacs-devel@gnu.org
>>
>> Pinging wasn't my intent, I just wanted to ask for review on
>> emacs-devel..
>
> Cross-posting on both bug-gnu-emacs and emacs-devel is generally not a
> good idea, so please try not to do that in the future. The people who
> are likely to review your patch are reading the bug list anyway.
Yes, I know that crossposting is not generally appreciated, but in this
case it's a bit different: I'm not posting the same message, rather I'm
creating a bug as a container for patch (I wanted to try debbugs
package, although I failed to do it properly, and the tagging message
went without patch - now I see where I was wrong, I didn't select the
commit _range_ with debbugs-gnu-pick-commits, but rather just a commit),
and the review request as an actual message.
What is best to do such things in the future? Just post a bug with tag
"patch", or just directly post patch to emacs-devel? I don't want to
cause inconvenience, sorry for this time.
Filipp
next prev parent reply other threads:[~2021-05-21 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2tumx6tm0.fsf@fastmail.fm>
[not found] ` <m28s496t4j.fsf@fastmail.fm>
[not found] ` <m2v97d5ed5.fsf@fastmail.fm>
2021-05-20 20:49 ` bug#48548: 28.0.50; Some process attributes on macOS are missing Filipp Gunbin
2021-05-21 5:53 ` Eli Zaretskii
2021-05-21 9:50 ` Filipp Gunbin
2021-05-21 10:27 ` Eli Zaretskii
2021-05-21 12:30 ` Filipp Gunbin [this message]
2021-05-21 12:33 ` Eli Zaretskii
2021-05-21 12:36 ` Filipp Gunbin
2021-05-21 12:45 ` Eli Zaretskii
2021-05-21 12:47 ` Filipp Gunbin
2021-05-21 12:47 ` Eli Zaretskii
2021-05-21 14:49 ` Basil L. Contovounesios
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pmxk46c1.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).