Displaying 4 results from an estimated 4 matches for "lot__".
Did you mean:
lot_
2020 Mar 03
3
Allowing PRs on GitHub for some subprojects
...dev wrote:
>> I know there has been significant discussion about "moving" from
>> Phabricator to GitHub reviews and pull requests, etc. I'm not
>> suggesting that we do anything in terms of global LLVM policy.
>> However, as a maintainer of libc++, I commit __a lot__ of other
>> people's code for them. It would be a huge time saver for me if I
>> could nicely suggest to contributors (not force them) to use PRs
>> instead of Phabricator for their contributions. It would also handle
>> commit attribution properly, which is a pain right...
2020 Feb 20
6
Allowing PRs on GitHub for some subprojects
Hi,
I know there has been significant discussion about "moving" from Phabricator to GitHub reviews and pull requests, etc. I'm not suggesting that we do anything in terms of global LLVM policy. However, as a maintainer of libc++, I commit __a lot__ of other people's code for them. It would be a huge time saver for me if I could nicely suggest to contributors (not force them) to use PRs instead of Phabricator for their contributions. It would also handle commit attribution properly, which is a pain right now.
Would it be possible to allow...
2020 Mar 03
3
Allowing PRs on GitHub for some subprojects
...gt;> I know there has been significant discussion about "moving" from
>>> Phabricator to GitHub reviews and pull requests, etc. I'm not
>>> suggesting that we do anything in terms of global LLVM policy.
>>> However, as a maintainer of libc++, I commit __a lot__ of other
>>> people's code for them. It would be a huge time saver for me if I
>>> could nicely suggest to contributors (not force them) to use PRs
>>> instead of Phabricator for their contributions. It would also handle
>>> commit attribution properly, which...
2020 Mar 04
3
Allowing PRs on GitHub for some subprojects
...there has been significant discussion about "moving" from
> >>> Phabricator to GitHub reviews and pull requests, etc. I'm not
> >>> suggesting that we do anything in terms of global LLVM policy.
> >>> However, as a maintainer of libc++, I commit __a lot__ of other
> >>> people's code for them. It would be a huge time saver for me if I
> >>> could nicely suggest to contributors (not force them) to use PRs
> >>> instead of Phabricator for their contributions. It would also handle
> >>> commit attribu...