search for: mydevelop

Sorry, I didn't notice this change of default last night. Thanks for fixing this! -- Mehdi On Tue, Jul 28, 2020 at 5:50 AM MyDeveloper Day via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I've made the change > > https://reviews.llvm.org/harbormaster/plan/5/ > > MyDeveloperDay <https://reviews.llvm.org/p/MyDeveloperDay/> changed the Hold > Drafts behavior for this plan from Always to Never....

This is configured in the "pre-merge checks" build plan, the "Hold Drafts" needs to be set to "Never" I should be able to change this in the build plan if you want but I don't want to step on anyone's toes MyDeveloperDay On Tue, Jul 28, 2020 at 1:35 PM MyDeveloper Day <mydeveloperday at gmail.com> wrote: > See the "Draft Mode" changes, might be related > https://secure.phabricator.com/w/changelog/2020.16/ > > MyDeveloperDay > > On Tue, Jul 28, 2020 at 1:32 PM Roman Lebedev...

Am Mi., 1. Juli 2020 um 05:46 Uhr schrieb MyDeveloper Day via llvm-dev <llvm-dev at lists.llvm.org>: > I always knew "polly" was mostly clean too, and actually one of the areas I already test against, (along with lib/Format obviously). You have no other choice. Polly verifies its source formatting as part of check-polly, so every...

Could we ever consider adding https://github.com/r4nt/phabricator/tree/llvm-production as a new read/only observe Diffusion repository in reviews.llvm.org? I'd be happy to do code reviews? MyDeveloperDay On Tue, Jul 28, 2020 at 8:46 PM MyDeveloper Day <mydeveloperday at gmail.com> wrote: > Awesome, thanks for sharing > > Here is a patch (based off yours) but this adds the "Collapse" button back > in, > > remember to rerun phabricator/bin/celerity map > &...

.../12 months period? I believe this process could be automated at least in a semi-automatic way. Once complete the pre-merge checks should maintain the current status. This would drive the goal of completely clang-formatted source tree, without the disruption to current active areas. Any thoughts? MyDeveloperDay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200628/28ed831f/attachment-0001.html>

...rmat. It would be good to get early warning of clang-format changes like that. Let me know if there is anything I can do to help. Tim From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> On Jun 28, 2020, at 8:30 AM, MyDeveloper Day via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: (Copying from Discourse) All A couple of months ago I added the following page documentation Clang-Formatted-Status<http://clang.llvm.org/docs/ClangFormattedStatus.html> to track the status...

...is present in the .clang-format file I realize it feels like unnecessary churn which is why I suggested this be in code which hasn't been touched in some time (I'd be fine if that time is 1+ years), but more often than not this is quite small basic style issues, similar to the ones below. MyDeveloperDay - void HandleTranslationUnit(ASTContext& context) override { + void HandleTranslationUnit(ASTContext &context) override { if (!Instance.getLangOpts().DelayedTemplateParsing) return; - std::set<FunctionDecl*> LateParsedDecls; + std::set<FunctionDecl *&...

Hi MyDeveloperDay, We are using the released version of clang-format / clang-tidy (not necessarily the latest release). I think it makes sense to use most recent versions of the tools: https://github.com/google/llvm-premerge-checks/issues/196 Kind regards, Mikhail On Wed, Jun 3, 2020 at 3:40 PM MyDeveloper...

On Tue, Jul 28, 2020 at 11:04 AM MyDeveloper Day <mydeveloperday at gmail.com> wrote: > Out of interest are you keeping the local modifications in a fork of the > Phabricator source (llvm-phabricator)? Firstly we should be keeping any > changes we make in source control but also it's good to review those > changes. &g...

On Tue, Jul 28, 2020 at 3:29 PM James Y Knight <jyknight at google.com> wrote: > > Please assume good faith -- I'm pretty sure this is simply a configuration mistake, since Mehdi just upgraded Phabricator to a new upstream revision last night. > Probably the default behavior changed in the new upstream version, and it just needs to be turned off. Yep, that's why i'm

...ws.llvm.org/D62616) I suspect it was created that way, and its only as the commit fires that it gets added. (it might be clearer if a herald rule so these are added at review creation, although anyone then removing them will get them readded at commit if they still have the incorrect repository.) MyDeveloperDay (Paul) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190603/f3d28201/attachment.html>

...wed By: jane doe,walter smith Subscribers: jane doe, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D58250 --------------------------------------------------------------------------------- You can then copy and paste this into your commit message. I hope this helps.. MyDeveloperDay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190302/a0464789/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: get_commit_message.sh Type: text/x-...

Hello, Is there a way for Phabricator to retain the patches as originally uploaded? When using the "Download Raw Diff" button, it seems Phabricator reformats the patch, loosing the parent commit along the way, so often patches don't apply. The following works, because I've got the latest checkout on master, and the patch was rebased recently: F:\llvm-project>curl

I filed a bug a long time ago here: https://bugs.llvm.org/show_bug.cgi?id=41559 It's an issue with how clang format isn't breaking function arguments as expected. I haven't seen a response. How can I go about getting the attention of the developers?

...cations (rL and rG). Before yesterday, this should have sent 3: one each for rL, rG, and rC. Projects not in the monorepo will get notifications for rL only. On Fri, May 31, 2019 at 2:15 AM Manuel Klimek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Fri, May 31, 2019 at 10:53 AM MyDeveloper Day <mydeveloperday at gmail.com> > wrote: > >> I actually run a in-house Phabricator instance with 400+ users and >> multiple git repo including custom extension developments >> >> I also follow the Phabricator development quite closely because we >> upg...

I actually run a in-house Phabricator instance with 400+ users and multiple git repo including custom extension developments I also follow the Phabricator development quite closely because we upgrade every couple of weeks I’d be more than happy to help maintain the phab instance for LLVM MyDeveloperDay On Fri, 31 May 2019 at 09:19, Manuel Klimek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Fri, May 31, 2019 at 10:11 AM Aaron Ballman <aaron.ballman at gmail.com> > wrote: > >> >> >> On Fri, May 31, 2019, 10:02 AM Roman Lebedev via ll...

...this should have sent 3: one > each for rL, rG, and rC. Projects not in the monorepo will get > notifications for rL only. > > > > On Fri, May 31, 2019 at 2:15 AM Manuel Klimek via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > On Fri, May 31, 2019 at 10:53 AM MyDeveloper Day <mydeveloperday at gmail.com> > wrote: > > I actually run a in-house Phabricator instance with 400+ users and > multiple git repo including custom extension developments > > > > I also follow the Phabricator development quite closely because we upgrade > every...

Hello friends, We are switching the pre-merge test build system from Jenkins to Buildkite. That will give authors and reviewers more transparency on what's going on during the build process. For now only members of "pre-merge beta testing" [0] group are affected. As usual, please tell us if something is off. [0] https://reviews.llvm.org/project/view/78/ Kind regards, Mikhail

On Tue, Jul 28, 2020 at 4:25 AM James Henderson < jh7370.2008 at my.bristol.ac.uk> wrote: > Thanks for the work too! > > Not specifically a regression, but since the upgrade, I find it annoying > now that when I want to do something in relation to an inline comment > (collapse it, reply to it etc), I now have to click on a drop-down menu in > the comment header bar to

Hi Tanya, Last time I noticed a problem with clang-tools-extra docs you could help solving them. If someone else is taking care of this part of the infrastructure now, please redirect appropriately. It looks like docs generated from rst (for LLVM, Clang and clang-tools-extra) don't get updated at the moment. They stopped updating somewhere between r353327