Date: Mon, 6 Feb 2017 21:43:39 +0100 From: Kurt Jaeger <lists@opsec.eu> To: Hiroki Sato <hrs@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: No reaction - what can I do? Message-ID: <20170206204339.GM13006@home.opsec.eu> In-Reply-To: <20170207.052701.822941695729815574.hrs@allbsd.org> References: <201702060901.v1691T6v084723@fire.js.berklix.net> <20170206.195956.1413994210073827079.hrs@allbsd.org> <20170206111716.GJ13006@home.opsec.eu> <20170207.052701.822941695729815574.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > li> [...] > li> > I am aware of this PR but I am still not sure of the cause since I > li> > could not reproduce it. > li> In this case, please write a note into the PR that you can > li> not reproduce it. It helps the submitter to understand the situation. > Okay, I will do it more actively. Honestly I was leaning to working > on upgrading TeXLive-related ports to the latest version instead of > fixing issues which I could not reproduce but it has taken a longer > time than I expected... I found, in the past, that if I can not reproduce something, if I then just add a "can not reproduce, please add more details" to a PR, that helps to get it closer to a solution -- because the reporter will try to add details and might find a solution himself. -- pi@opsec.eu +49 171 3101372 3 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170206204339.GM13006>