Displaying 7 results from an estimated 7 matches for "biryukov".
2019 Jan 15
2
Proposal for an alternative bugtracking workflow
...aving this supported by GitHub would mean a much better UX...
On Tue, Jan 15, 2019 at 3:09 PM James Y Knight <jyknight at google.com> wrote:
> BTW, Google search found this tool:
> https://github.com/bcongdon/github-label-notify
>
>
>
> On Tue, Jan 15, 2019, 8:02 AM Ilya Biryukov via llvm-dev <
> llvm-dev at lists.llvm.org wrote:
>
>> On Tue, Jan 15, 2019 at 1:47 PM Chandler Carruth <chandlerc at gmail.com>
>> wrote:
>>
>>> Has anyone reached out to GitHub about potentially enabling this?
>>>
>> For the lack of a bett...
2019 Jan 15
2
Proposal for an alternative bugtracking workflow
...addressing basic missing functionality
> like notifications.
>
> Ilya, can you forward whatever ticket or tracking entry there is here? I'd
> love to try and surface the critical nature of this for the LLVM project to
> GitHub folks.
>
> On Tue, Jan 15, 2019 at 8:03 AM Ilya Biryukov <ibiryukov at google.com>
> wrote:
>
>> The script queries **all** issues with specified labels and "notifies" on
>> each of those.
>> While this approach works, I doubt it would scale well if everyone is
>> doing this by hand. OTOH, building a service...
2019 Jan 15
2
Proposal for an alternative bugtracking workflow
...ue, Jan 15, 2019 at 1:47 PM Chandler Carruth <chandlerc at gmail.com>
wrote:
> Has anyone reached out to GitHub about potentially enabling this?
>
For the lack of a better place, filed a ticker against GitHub support. Will
update the thread when they come back to me.
--
Regards,
Ilya Biryukov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190115/9a3c2635/attachment.html>
2019 Jan 14
2
Proposal for an alternative bugtracking workflow
...thub.com/llvm/llvm-project' repository will be used to solely host the
code, it will not have an issue tracker associated with it.
Do you think this workflow would be a good fit for tracking bugs in LLVM?
[1]: http://lists.llvm.org/pipermail/llvm-dev/2018-October/127068.html
--
Regards,
Ilya Biryukov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190114/da69c535/attachment.html>
2019 Jan 15
3
Proposal for an alternative bugtracking workflow
+llvm-dev
On Mon, Jan 14, 2019 at 1:46 PM David Chisnall <David.Chisnall at cl.cam.ac.uk>
wrote:
> On 14/01/2019 10:36, Ilya Biryukov via llvm-dev wrote:
> > To reiterate, our proposal was to create a repository for each of the
> > LLVM subprojects under the official LLVM GitHub account, e.g.
> > github.com/llvm/clangd <http://github.com/llvm/clangd>.
> > This repository would be run by the part of t...
2011 Nov 01
1
Error on the site
Good afternoon.
I apologize for my English.
Error on page: http://libvirt.org/formatdomain.html
To be more precise in the line "<target *def*='hdc' bus='ide'/>"
--
Biryukov Alexander
ICQ: 467093457
Skype: reddog_gad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20111101/9a6e7c0b/attachment.htm>
[llvm] r322838 - [ADT] Split optional to only include copy mechanics and dtor for non-trivial types.
2018 Jan 24
1
[llvm] r322838 - [ADT] Split optional to only include copy mechanics and dtor for non-trivial types.
On Wed, Jan 24, 2018 at 11:47 PM, Benjamin Kramer <benny.kra at gmail.com>
wrote:
> That's an unintentional change. However, the reason for this change
> was to make optional of trivially copyable types trivially copyable,
> adding a user-provided move ctor would break that again :(
>
> I'm leaning towards making the non-trivial version of llvm::Optional
> more