Date: Tue, 31 Jan 2023 22:05:30 -0800 From: Yetoo <yetoohappy@gmail.com> To: David Chisnall <theraven@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: GitHub Code Search [Re: Tooling Integration and Developer Experience] Message-ID: <CALT2f4uCWixpkOntX5pJzhp1Lj6x9Yizfd1pcBapdruDNyvqGQ@mail.gmail.com> In-Reply-To: <fc67ae75-4b66-6f03-7c90-571252c65676@FreeBSD.org> References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <CALT2f4vNTQkiDp-4KOg-2E32CFKpcycih=yaR96ocWR30jCr6A@mail.gmail.com> <fc67ae75-4b66-6f03-7c90-571252c65676@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Tue, Jan 31, 2023, 9:47 AM David Chisnall <theraven@freebsd.org> wrote: > > On 30/01/2023 21:39, Yetoo wrote: > > > > If github is going to be considered for issue tracking I just want to > > say, after having extensively using it for issue tracking, it tends to > > be difficult to find an issue if the exact title isn't entered and many > > duplicate reports are made as a result. Code search sucks and doesnt > > show you the multiple places in a file where a match was made so a user > > may be left wondering if code exists or not, but this doesn't seem to be > > germane given this is about issue tracking. > > Which search are you using? The old GitHub search is not great, but > cs.github.com has replaced local search for me in the FreeBSD tree. > It's not *quite* as good as fxr, but it's close. > > For example, searching for sys_cap_enter: > > https://cs.github.com/?scopeName=All+repos&scope=&q=sys_cap_enter+repo%3Afreebsd%2Ffreebsd-src+ > > David Clicking that link greets me with a login screen and a requirement to join a waitlist. Yes, this is beta and may change in the future, but not thrilled that an account is required to use and opt into it.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALT2f4uCWixpkOntX5pJzhp1Lj6x9Yizfd1pcBapdruDNyvqGQ>