-- Forwarded message -
From: Konrad Kleine
Date: Tue, 21 Apr 2020 at 09:39
Subject: Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues
[UPDATED]
To: Tom Stellard
Hi Tom.
I haven't read all the replies before mine. Sorry if my idea overlaps with
someone else's.
I have
Similar to other people's experiences, I've worked on a common code base
that supported three different platforms, and each platform used a
different bugzilla with it's own numbering scheme. I regularly came across
references to "BZ123456" with no indication as to which of the three
systems that re
Since Bugzilla numbers are all under 50,000 (at least for now:), can't we
simply bump the GitHub issue/pull request numbers to 50,000, and start from
there?
Then it would be easy to identify: < 5 means Bugzilla, >= 5 means
GitHub.
Now somebody's only gotta find a way to file 5-200
I wanted to try importing llvm bugs into a fresh github repo and here's my
result so far (import is still running):
https://github.com/kwk/test-llvm-bz-import-4 . I've written the scripts (
https://github.com/kwk/bz2gh) myself because I wanted to remain in control
and don't make my life more compli
Hi Konrad,
Thanks for the scripts – look useful! For the record, here is the
result of previous experiments
https://github.com/asl/llvm-bugzilla/issues
On Wed, Apr 22, 2020 at 2:21 PM Konrad Kleine via cfe-dev
wrote:
>
> I wanted to try importing llvm bugs into a fresh github repo and here's my
GitHub canonically uses "#NNN" to refer to its bugs or pull requests, and
also supports "GH-NNN". We'll want to switch to one of those schemes, so
that automatic linking works properly. So, in that case, PR1234 == legacy
issue, #1234 or GH-1234 == new issue.
(See
https://help.github.com/en/github/
GitHub also supports custom prefixes for the issues. However, here is
another limitation: the prefix must be at least 3 letters, so we
cannot, for example, autolink PR1234 issues. Already asked whether
this restriction could be lifted.
On Wed, Apr 22, 2020 at 3:15 PM James Y Knight via llvm-dev
w
Github may do things in a canonical way, but I think you'll find that lots
of people will refer to them by other means in review comments, email
threads, etc. Let's avoid any risk of ambiguity...
Also, there's no guarantee in the future that Github won't decide to start
auto-linking PR1234 as well
Custom prefixes are intended for autolinks to external systems -- I suspect
it would not work properly (but have not tested) if you used it to refer
back to github itself. E.g. putting reverse links in issues you refer to,
or closing an issue when writing "closes CUSTOM-123" in a commit message.
O
On 4/21/20 6:50 PM, Richard Smith wrote:
On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev
mailto:llvm-...@lists.llvm.org>> wrote:
On 04/21/2020 03:36 PM, Richard Smith via llvm-dev wrote:
> On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev
mailto:cfe-...@lists.llvm.org
On 04/21/2020 06:50 PM, Richard Smith wrote:
> On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev
> mailto:llvm-...@lists.llvm.org>> wrote:
>
> On 04/21/2020 03:36 PM, Richard Smith via llvm-dev wrote:
> > On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev
> mailto:cfe-...@list
On 04/21/2020 03:36 PM, Richard Smith via llvm-dev wrote:
> On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev
> mailto:cfe-...@lists.llvm.org>> wrote:
>
> +1 to James's take
>
> I'd prefer simplicity of implementation over perfection here.
>
> If we end up with two different bug n
On Wed, 22 Apr 2020 at 09:45, Philip Reames via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> On 4/21/20 6:50 PM, Richard Smith wrote:
>
> On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
>> On 04/21/2020 03:36 PM, Richard Smith via llvm-dev wrote:
>> > On
On 4/22/20 2:35 PM, Richard Smith wrote:
On Wed, 22 Apr 2020 at 09:45, Philip Reames via cfe-dev
mailto:cfe-...@lists.llvm.org>> wrote:
On 4/21/20 6:50 PM, Richard Smith wrote:
On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev
mailto:llvm-...@lists.llvm.org>> wrote:
https://bugs.llvm.org/show_bug.cgi?id=45642
Bug ID: 45642
Summary: Step over misbehaves with multiple threads on Linux
Product: lldb
Version: 10.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
15 matches
Mail list logo
