From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 90008 invoked by alias); 13 Sep 2017 18:44:24 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 88745 invoked by uid 89); 13 Sep 2017 18:44:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=kawa, unsure X-HELO: aibo.runbox.com Received: from dns3.teletopia.net (HELO aibo.runbox.com) (91.220.196.211) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 13 Sep 2017 18:44:21 +0000 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dsCe2-0005jc-9S; Wed, 13 Sep 2017 20:44:18 +0200 Received: from 70-36-239-177.dsl.dynamic.fusionbroadband.com ([70.36.239.177] helo=localhost.localdomain) by mailfront12.runbox.com with esmtpsa (uid:757155 ) (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) id 1dsCdq-0003Zx-1w; Wed, 13 Sep 2017 20:44:06 +0200 Subject: Re: best way for reporting issues To: Sonny To , Kawa mailing list References: From: Per Bothner Message-ID: Date: Wed, 13 Sep 2017 18:44:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-q3/txt/msg00037.txt.bz2 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/