From: Alex Gramiak <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>, spacibba@aol.com, emacs-devel@gnu.org
Subject: Re: bug#34798: acknowledged by developer (Re: bug#34798: 27.0.50; xclip issue in tramp mode)
Date: Tue, 16 Apr 2019 10:55:32 -0600 [thread overview]
Message-ID: <87ftqhdh4r.fsf@gmail.com> (raw)
In-Reply-To: <835zregctj.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Apr 2019 19:00:24 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Tue, 16 Apr 2019 16:34:54 +0200
>> Cc: emacs-devel@gnu.org
>>
>> admin/notes/bugtracker has a description of the bugtracker
>> commands. Perhaps we should add a pointer to it to CONTRIBUTE.
>
> CONTRIBUTE has a narrower audience than those who might need to know
> how to work with the bug tracker, so I don't think CONTRIBUTE is the
> right place.
On the other hand, a valid place to contribute is to work with the bug
tracker to triage bugs, no? Adding a separate section in CONTRIBUTE for
some common commands would be helpful in that case.
next prev parent reply other threads:[~2019-04-16 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 23:11 bug#34798: 27.0.50; xclip issue in tramp mode Ergus
2019-03-11 20:16 ` Stefan Monnier
2019-03-12 22:44 ` Ergus
2019-03-13 7:23 ` Michael Albinus
2019-04-16 1:17 ` Noam Postavsky
2019-04-16 7:10 ` Michael Albinus
[not found] ` <handler.34798.C.1555377435564.notifdonectrl.0@debbugs.gnu.org>
2019-04-16 14:16 ` bug#34798: acknowledged by developer (Re: bug#34798: 27.0.50; xclip issue in tramp mode) Ergus
2019-04-16 14:34 ` Robert Pluim
2019-04-16 16:00 ` Eli Zaretskii
2019-04-16 16:55 ` Alex Gramiak [this message]
2019-04-16 15:05 ` Eli Zaretskii
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=87ftqhdh4r.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
--cc=spacibba@aol.com \
/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.