From: Per Bothner <per@bothner.com>
To: Sonny To <son.c.to@gmail.com>, Kawa mailing list <kawa@sourceware.org>
Subject: Re: best way for reporting issues
Date: Wed, 13 Sep 2017 18:44:00 -0000 [thread overview]
Message-ID: <d8ee93d8-e3e7-aa37-6fd3-4f921fd5dcbb@bothner.com> (raw)
In-Reply-To: <CAJxjsJukkpnL1qYD9Cc+w7m-FQ++E7isfKhs_QkgU_8dOwA4zg@mail.gmail.com>
On 09/13/2017 06:30 AM, Sonny To wrote:
> It seems the mailinglist is used to report issue. I reported an issue
> via gitlab https://gitlab.com/kashell/Kawa/issues/20 I think its
> better than using email for reporting and tracking issues.
>
> what is the prefered way?
In general creating a GitLab issue is preferable as I'm less likely to forget
or "lose" the issue. Plus when/if it is fixed, it is good to refer to the issue
for both the fix and the testcase.
Sometimes using email makes sense. For example when asking for help or whether
something works for others, or if you're unsure if you're doing something right.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2017-09-13 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 13:30 Sonny To
2017-09-13 18:44 ` Per Bothner [this message]
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=d8ee93d8-e3e7-aa37-6fd3-4f921fd5dcbb@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=son.c.to@gmail.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.
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).