search for: ccing

For some users on my site I'd like to be able to CC a particular user on all outgoing IMAP mails. Incoming I can do but don't see how to do outgoing. Ideas? Dave -- It is told that such are the aerodynamics and wing loading of the bumblebee that, in principle, it cannot fly...if all this be true...life among bumblebees must bear a remarkable resemblance to life in the United

With the numbers of patches flying around it can be a bit hard for a maintainer to spot patches which (s)he is expected to comment on / deal with, especially now that we have a larger number of maintainers of varying subsystems etc. I think it might be time to start asking patch submitters to CC the maintainers of the code they are touching, based on the MAINTAINERS file. If people (specifically

I vote for spec''ing. Anybody else?

I''m CCing zfs-discuss at opensolaris.org, as this doesn''t look like FreeBSD-specific problem. It looks there is a problem with block allocation(?) when we are near quota limit. tank/foo dataset has quota set to 10m: Without quota: FreeBSD: # dd if=/dev/zero of=/tank/test bs=512 count=20480 tim...

Hi folks (CCing llvm-dev, but that's probably more of a cfe-dev topic), As a follow-up to that old thread about -D_FORTIFY_SOURCE=n http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html And, more recently, to this fedora thread where clang/llvm -D_FORTIFY_SOURCE support is claimed to be only...

...3 at 19:51 -0500, Misha Brukman wrote: > The second one is a "serious policy violation", which isn't as clear to > me what the bug reporter is saying, but it mentions warnings during > doxygen build and missing fonts and related issues that I'm not quite > following. (CCing the bug and thus the submitter) sounds like a missing built-depends, at least graphviz, possibly something else. Could you give us some of the error output from your build to help narrow things down? Thanks Andrew Lenharth andrewl at debian.org alenhar2 at cs.uiuc.edu

On Sun, Jan 09, 2005 at 02:03:28AM -0200, Henrique de Moraes Holschuh wrote: > *AND* there is a major problem with liboggflac1. > > liboggflac1 did not change the soname (better check this, it might require a > soname change, check the seekable ogg-flac support stuff). CCing upstream on this. Josh, did 1.1.1 change interfaces in liboggflac? If so, it needs a soname change. > If it does, a new upload fixes it, and liboggflac1 should be generated by > the old-flac package. If it doesn't, then what should we do? libflac4 > would be mostly useless in that...

On Wed, 8 May 2019 at 04:52, Peter Langfelder <peter.langfelder at gmail.com> wrote: > > (CCing the R-devel list, maybe someone will have a better answer.) > > To be honest, I don't know how to. I wasn't able to configure R to use > OpenBLAS using the configure script and options on my Linux Fedora system. > I configure it without external BLAS, then replace the libRblas.d...

Hi Everyone, According to this CVE: http://lists.xen.org/archives/html/xen-announce/2012-06/msg00001.html The patch has been added to xen-3.4-testing.hg. However, when I look here: http://xenbits.xen.org/hg/xen-3.4-testing.hg/ I don''t see any recent commits. Am I missing something? I feel it is very important that these patches make its way into this branch, and tagged as 3.4.5

...ections for increasing swap here: > http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Resizing_ZFS_Swap_and_Dump_Devices if I understand correctly, in your case the failure occurs when you try to increase swap size by means of ''zfs set volsize'' command ? CCing ZFS team. Thank you, Jan

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

...n memory. Adding support for a non-moving gc with register roots would not be too hard and might be possible to reuse some of the recent stackmap work. For a moving GC you would probably have to change how we represent pointer arithmetic in the selection dag and MI. It would be quiet a big change. CCIng Andy and Patrick since they might have an idea of how much work that would be and what the costs and benefits for LLVM are. Also to note is that there are plans to move away from selection dag, so it might be good to sync this work with whatever we end up using instead. Cheers, Rafael

On Fri, Jun 27, 2014 at 8:13 AM, Yaron Keren <yaron.keren at gmail.com> wrote: > Happened to me twice, it would be really nice if Phab would require > confirmation of patches created without CCing one of the two lists, > something like: > > "You have not CCed llvm-commits or cfe-commits, are you creating a private > patch?" > I filed https://secure.phabricator.com/T5495 Cheers, /Manuel > > Yaron > > > 2014-06-27 0:40 GMT+03:00 Justin Bogner <mai...

Hi, Header says: /* * Unmaps the @count pages starting at @start_address, which were mapped by a * call to xc_gntshr_share_*. Never logs. */ int xc_gntshr_munmap(xc_gntshr *xcg, void *start_address, uint32_t count); But implementation calls: static int linux_gntshr_munmap(xc_gntshr *xcg, xc_osdep_handle h, void *start_address, uint32_t count) { return

On 10/30/13 7:09 PM, Philip Reames wrote: > David, Quentin - Thanks for the feedback. Responses inline. > > On 10/30/13 11:21 AM, David Blaikie wrote: >> Actually CCing Eric. >> >> >> On Wed, Oct 30, 2013 at 11:00 AM, Quentin Colombet >> <qcolombet at apple.com <mailto:qcolombet at apple.com>> wrote: >> >> Philip, >> >> Thanks for the clarification. >> >> As far as I can tell, the...

...be fine in case they were compiled > | > with older version of gfortran-8, but then the next rebuild will cause > | > trouble): Dirk, any chance you could get the package maintainers to make > | > these changes? > | > | It seems to me this is of relevance for for S?bastien (Ccing), or more > | generally for debian-science. > Not really. I do not think anybody concluded our LAPACK/BLAS needed to be > recompiled. The discussion about this has been going on for a few weeks and > is now also between gcc/gfortran upstream and the lapack folks. See Tomas's >...

...ust go with TMPDIR if it's > set and non-empty, and then fall back to confstr. However, we should not be > using TMPDIR if ErasedOnReboot is false (i.e. if we'd prefer > _CS_DARWIN_USER_CACHE_DIR). Unfortunately there's no canonical environment > variable for that. > > CCing Greg to see if that makes sense. OK, so I guess something like this? Cheers, Rafael -------------- next part -------------- A non-text attachment was scrubbed... Name: t.patch Type: text/x-patch Size: 7578 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201...

LLVM developers: Does anyone have time and interest to review a libc++ change? https://reviews.llvm.org/D26920 Eric