search for: cc'ing

Seems to be largely untested... anyone using this? (cc'ing Kevin as he's the most likely candidate). At the least for MCAnalysis this appears to be unused, any ideas on what else can be deleted? I'll remove just this file unless there are objections tomorrow (or earlier if I get an ack from Kevin about it). -eric

On Nov 14, 2012, at 10:52 AM, Sean Silva <chisophugis at gmail.com> wrote: > It references release 2.7... is this document worth keeping? > Nuke it from orbit. :) > CC'ing Jim Grosbach since IIRC he recently pulled out some stuff > related to llvm-gcc. > > -- Sean Silva

(Sorry for CC'ing piles of people, but didn't want folks to miss this in the mailing list churn.) See the subject. The problem is in the target-independent code generator and especially in the x86 backend. I would like to fix it. This will be a mechanical change just organizing code in a way that makes...

Doesn't seem to get a lot of love since most of the commits in the last 3 years have been maintenance. I guess it doesn't take a whole lot of maintenance either, but... cc'ing Wesley since he seems to be the last guy to commit to it. Thoughts? -eric

...hard, If you want to plot both datasets on the same plot just make use of the xyplot for FLQuants, something like flqs <- FLQuants(list(pred=pred.quant, res=res.quant)) xyplot(data~age, data=flqs) now tune it the way you want and change the formula to fit your needs. Regards EJ ps: I'm cc'ing this to the mailing lists, I find it usefull for others.

...hard, If you want to plot both datasets on the same plot just make use of the xyplot for FLQuants, something like flqs <- FLQuants(list(pred=pred.quant, res=res.quant)) xyplot(data~age, data=flqs) now tune it the way you want and change the formula to fit your needs. Regards EJ ps: I'm cc'ing this to the mailing lists, I find it usefull for others.

On 4 February 2017 at 02:58, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think that LLD is going to be included in the 4.0 release. At least, we've > been cherry-picking fixes into the release branch. I've CC'd some others > that will know the details. The test-release.sh script still doesn't have it and I believe it's just because we never had it, but I agree we should release it this time. It's good enough to at least be considered beta in some arches and experimental in others. C...

.../D12761>, I've created a new revision. The attached diff is a very a slightly modified version of your original patch ... I have wanted to reopen a Phabricator revision too many times already, but couldn’t. I don’t know who the admin of reviews.llvm.org <http://reviews.llvm.org/> is (CC’ing Chandler as my wild guess). Could we configure it so that revisions can be reopened? Kuba -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160607/90fe37bc/attachment.html>

...e an announcement on the > list though ;) > > Chris - Can you comment on list why you made this change? Sorry, sure. The basic problem it solves is that many people read the commits list (in particular) only infrequently. They post frequently due to commits, and having them in the CC line makes them notice it faster. I was manually cc'ing the person I was responding to on a ton of emails. I consider this to be silly and took mailman's advice of not forcing the reply-to line. -Chris

...ng. Release blockers are tracked by https://llvm.org/PR35804 Please mark any bugs, old or new, that need to be fixed as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be merged --- ideally by filing a blocker bug on PR35804, or by cc'ing me on the commit email. Please help out with the release by notifying me of any bugs, commits, or other issues you thin k might be relevant. If it's not marked as blocking PR35804, or I'm not cc'd on an email about it, I'll probably miss it. Thanks, Hans

...gs, old or new, that you think need to be fixed before the release as blocking that. Please help out with the release by notifying me of any bugs, commits, or other issues you think might be relevant; ideally by marking them as blockers of the bug above. If it's not on that bug, or I'm not cc'd on an email about it, I'll probably miss it. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be merged -- ideally by filing a blocker bug on PR33849, or by cc'ing me on the commit email. What's next? Once the branch is in good s...

...ly due to the fact that some of the values in x[,1] are empty ("") I would like to get a "NA" for these values, and the found value for those where mget finds one. Could anyone tell me how this is done efficiently? Thanks a lot in advance! Georg P.S. I am in digest mode, cc'ing the answer directly to me would be nice -- Georg Wilhelm Otto Max-Planck-Institute for Developmental Biology Spemannstrasse 35/III D-72076 Tuebingen Germany phone: +49-7071-601 401 http://www.eb.tuebingen.mpg.de

...I pointed out, 'Means, Jeffrey D' has probably never registered to post on the Samba mailing list and his posts are probably stuck in moderation and may suddenly appear at some point. That will make it three problems with his posts: Posting without registering. Hijacking a thread. Finally, CC'ing a Samba user, unless requested, you should only send posts to the list. Rowland

...is not a > directory . > > Just a bit more info and I can get back to you if I’m using what your > asking about. > > Kev > > On Jul 31, 2014, at 1:13 PM, Eric Christopher <echristo at gmail.com> wrote: > > > Seems to be largely untested... anyone using this? (cc'ing Kevin as > > he's the most likely candidate). At the least for MCAnalysis this > > appears to be unused, any ideas on what else can be deleted? > > > > I'll remove just this file unless there are objections tomorrow (or > > earlier if I get an ack from...

...rk in practice depends on a few more details. To Keep it short: * Linux: works out of the box * macOS: possible, but cumbersome (the example is not up-to-date here) * Windows: I lost hope (haven't looked at it for a long time though) Best Stefan Am 13.07.18 um 21:00 schrieb Alex Denisov: > cc'ing Stefan Gränitz, he had some progress on this topic. > >> On 13. Jul 2018, at 18:39, Geoff Levner via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Greetings, LLVM wizards. >> >> I was just wondering if any progress has been made on this issue in t...

> On Mar 31, 2020, at 10:55 AM, David Blaikie <dblaikie at gmail.com> wrote: > > +1 to all that & cc'ing a few of the usual suspects as FYI > > On Tue, Mar 31, 2020 at 10:36 AM Pavel Labath via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > > For me personally, the ability to write/edit syntactically correct dwarf > easily...

...tached diff is a very a slightly > >> modified version of your original patch ... > > > > I have wanted to reopen a Phabricator revision too many times already, > > but couldn’t. I don’t know who the admin of reviews.llvm.org > > <http://reviews.llvm.org> is (CC’ing Chandler as my wild guess). Could > > we configure it so that revisions can be reopened? > > Manuel is the one to CC. > > Tobias > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/...

https://godbolt.org/g/VvrbFZ For the code below generated assembly is the worst possible - test 1, else test 3, else test 2 with expected value of 2 last ... Whats going on? long case_2(); long case_3(); long case_1(); long case_else(); long test(long a) { switch (__builtin_expect(a, 2)) { case 2: return case_2(); case 3: return case_3(); case 1: return case_1();

...https://llvm.org/PR42474 Please mark any bugs, old or new, that need to be fixed before the release as blocking that. To get a change committed to the branch, first commit it to trunk as usual, and then request it to be merged --- ideally by filing a blocker bug on https://llvm.org/PR42474, or by cc'ing me on the commit email. (Please don't request merges over IRC; there's a high risk I'll miss them.) Please help with the release by notifying me about any bugs, commits, or other issues you think might be relevant. If it's not already tracked as a blocker of the release bug...

I'd like to be able to deliver certain mail as 'read' from procmail. My procmail rules call deliver with -m to directly to inject filtered mail to maildir based directories. I like to keep copies of mail I've sent by cc'ing it to myself and using procmail to filter and store copies in the appropriate directory. I cannot seem to find a way of delivering cc'd mail from me to me as 'read'. I'm running dovecot-1.0.7-2.el5 on a CentOS 5 distribution. Any hints on how I may achieve this are we...