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:36:34 +0300 [thread overview]
Message-ID: <m2y2c86z71.fsf@fastmail.fm> (raw)
In-Reply-To: <83o8d4mfke.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 May 2021 15:33:53 +0300")
On 21/05/2021 15:33 +0300, Eli Zaretskii wrote:
>> From: Filipp Gunbin <fgunbin@fastmail.fm>
>> Cc: emacs-devel@gnu.org
>> Date: Fri, 21 May 2021 15:30:38 +0300
>>
>> 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.
>
> Just post to the bug list and wait for responses. If you see no
> responses in a week or two, ping the bug list. If that doesn't
> receive any responses, either, ask on emacs-devel about the bug.
You mean normal M-x report-emacs-bug, or just posting to the list?
next prev parent reply other threads:[~2021-05-21 12:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 20:24 bug#48548: 28.0.50; Some process attributes on macOS are missing Filipp Gunbin
2021-05-20 20:35 ` Filipp Gunbin
2021-05-20 20:39 ` Filipp Gunbin
2021-05-20 20:49 ` 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
2021-05-21 12:33 ` Eli Zaretskii
2021-05-21 12:36 ` Filipp Gunbin [this message]
2021-05-21 12:45 ` Eli Zaretskii
2021-05-21 12:47 ` Eli Zaretskii
2021-05-21 14:49 ` Basil L. Contovounesios
2021-05-21 12:47 ` Filipp Gunbin
2021-05-25 4:08 ` Lars Ingebrigtsen
2021-05-25 17:13 ` Filipp Gunbin
2021-05-25 19:32 ` Lars Ingebrigtsen
2021-05-26 6:52 ` Alan Third
2021-05-26 14:12 ` Filipp Gunbin
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=m2y2c86z71.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 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.