* best way for reporting issues
@ 2017-09-13 13:30 Sonny To
2017-09-13 18:44 ` Per Bothner
0 siblings, 1 reply; 2+ messages in thread
From: Sonny To @ 2017-09-13 13:30 UTC (permalink / raw)
To: Kawa mailing list
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: best way for reporting issues
2017-09-13 13:30 best way for reporting issues Sonny To
@ 2017-09-13 18:44 ` Per Bothner
0 siblings, 0 replies; 2+ messages in thread
From: Per Bothner @ 2017-09-13 18:44 UTC (permalink / raw)
To: Sonny To, Kawa mailing list
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/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-09-13 18:44 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-09-13 13:30 best way for reporting issues Sonny To
2017-09-13 18:44 ` Per Bothner
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).