search for: uncool

...e code isn't hitting llvm-commits or cfe-commits where the majority of code maintainers use the mailing lists for review. At this point I think Phabricator should be disabled and patches should be send to the mailing lists *until* the technical issue is confirmed resolved. It's really uncool that code is entering ToT through this back-channel -- I appreciate that it might not be intentional, but every single patch that gets committed this way is a real problem for the project. Alp. -- http://www.nuanti.com the browser experts

...ts where the majority of code maintainers use the mailing lists for >> review. >> >> At this point I think Phabricator should be disabled and patches should be >> send to the mailing lists *until* the technical issue is confirmed resolved. >> >> It's really uncool that code is entering ToT through this back-channel -- I >> appreciate that it might not be intentional, but every single patch that >> gets committed this way is a real problem for the project. >> >> Alp. >> >> -- >> http://www.nuanti.com >> the br...

...linker work. But the target data layout is target specific. My bitcode file should not be. The only critical thing in the layout is the pointer size: "p:32:32" vs "p:64:64". Is there a way to use placeholders to insert the bit width of a pointer at a very late stage? It would be uncool when the platform independence of a bitcode file fails at _one_ single line. Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110925/04131c3a/attachment.html>

Hi, I'm just curious how to force usernames to be modified to lowercase letters if one mixes uper and lower case letters to one salad? Cause my SpamAssassin gets confuesd and treats different spellings of Usernames as different Users - which is uncool. I've heard about something you can add in your dovecot.config to enforce lowercase letters only. Thanks

You probably know this already, but the following notice appeared to bugtraq. As a side note the protocol on bugtraq seems to be designed to make a fix available before the announcement by providing one yourself or giving the maintainer a week's advance warning (M$ gets a lot longer warning and *still* fails to fix the bugs before bugtraq knows). Having said that M$ insists on allowing me

...its where the majority of code maintainers > use the mailing lists for review. > > At this point I think Phabricator should be disabled and patches > should be send to the mailing lists *until* the technical issue is > confirmed resolved. > > It's really uncool that code is entering ToT through this > back-channel -- I appreciate that it might not be intentional, but > every single patch that gets committed this way is a real problem > for the project. > > > Phabricator has certainly had its share of technical difficulties &...

Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE usage we could convert to WARN_ONCE? Reviewed-By: Karol Herbst <karolherbst at gmail.com> On Fri, Jul 14, 2017 at 5:05 PM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > On 7/14/17 3:41 PM, Mike Galbraith wrote: >> >> On Fri, 2017-07-14 at 15:36 +0200, Mike Galbraith wrote:

...m inside the directory and point your browser at: http://localhost:5555/ The fly in the ointment is that until a Comet request finishes, that URL mount point stops responding. I assume this is because of how thread management happens in Mongrel. Leaving the request unfinished like I do is probably uncool. One way to sort of work around the problem is to use a dispatcher that registers a new handler at a unique URL for each Comet user. You can see that both the main page and: http://localhost:5555/2 work simultaneous. And neither affects other mounted handlers, so you can also access: http://loc...

I am a newbie to samba. I have successfully setup a similar samba share on 1 machine in the past. I have everything setup as User access with the pcguest as a guest account. If I create a share to the /tmp, network users can access normally. I created a directory /var/snd and set permissions to be rwxrwxrwx. I changed the smb.conf so that permission were identical to the share for /tmp. I

Hi, Apparently, guestmount -o allow_other -a "/path/to/raw_file" -m /dev/sda1 "/path/to/mountfolder" is much slower than kpartx -av "/path/to/raw_file" mount /dev/mapper/loop0p1 /path/to/mountfolder (Doing lots of read/write inside the image.) I thought guestmount "only" scripts the above. Seems I was wrong on that. I am currently using

...1:15 AM, Mike Galbraith <efault at gmx.de> wrote: > On Fri, 2017-07-14 at 17:10 +0200, Karol Herbst wrote: >> Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE >> usage we could convert to WARN_ONCE? > > Shooting the messenger is generally considered uncool :) That's never stopped it from being a popular practice...

On Fri, 2017-07-14 at 17:10 +0200, Karol Herbst wrote: > Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE > usage we could convert to WARN_ONCE? Shooting the messenger is generally considered uncool :) -Mike

Hello, I''m looking for info on adding a disk to my current zfs pool. I am running OpenSoarlis snv_98. I have upgraded my pool since my image-update. When I installed OpenSolaris it was a machine with 2 hard disks (regular IDE). Is it possible to add the second hard disk to the pool to increase my storage capacity without a raid controller? >From what I''ve found, the

...ver. This has worked perfect for a long time! Until my upgrade to 3.1p2 the ssh1 system correctly asked the remote server at the end of the line for a name (and a host key). The remote server name was the key in the host table. Now, however, ssh saves the key under localhost!!! This is really uncool since I easily run five tunnels to five different remote servers (on five local port no's), so...... Whoever changed it.... Is this a bug, or am I using ssh in the wrong way! Thanks, - Jakob Lichtenberg ------- You are receiving this mail because: ------- You are the assignee for the bug...

...convert nil into a string. (That is patently false, but we''ll just nod our heads and move on.) So... what''s a guy to do? Use the traditional link_to format? link_to(''Delete'', :action => ''delete'', :id => @page) That''s totally uncool. I''m already having nightmares about the nightmares I''ll have trying to remember when to use which technique. (Not to mention trying to explain this to my co-worker (who''s more of a newbie than I am).) If there were a delete_page_url function that accepted :get as its...

...all the FUSE layers, and should be quite a lot faster. (2) Use UML instead of qemu. This requires you to update your version of libguestfs to something more recent (1.24 ideally), and follow the instructions here: http://libguestfs.org/guestfs.3.html#user-mode-linux-backend UML might be "uncool", but the UML backend is fully tested for each release and supported by us. UML has the advantage that its performance is reasonably consistent between baremetal and under virtualization. (3) Run libguestfs on baremetal (!) I'd love to say that you could use nested virtualization to get...

I hope this off topic post is ok I just find out this new service that provides free internet and free device

...ry.statistics") test3 <- parSapply(cl, l, fun) # error! ########## I found a solution somewhere in a forum: clusterCall(cl, function() library("ergm")) However, as I'd like to use the code in a package, the CRAN check tells me that using library calls inside a package is uncool. So I guess there must be another solution? Thanks in advance for any hints. Best, Philip (University of Bern)

...t;> >> review. >> >> >> >> At this point I think Phabricator should be disabled and patches >> should be >> >> send to the mailing lists *until* the technical issue is confirmed >> resolved. >> >> >> >> It's really uncool that code is entering ToT through this back-channel >> -- I >> >> appreciate that it might not be intentional, but every single patch >> that >> >> gets committed this way is a real problem for the project. >> >> >> >> Alp. >> >&g...

...e mailing lists for review. > > At this point I think Phabricator should be disabled and > patches > should be send to the mailing lists *until* the technical > issue is > confirmed resolved. > > It's really uncool that code is entering ToT through this > back-channel -- I appreciate that it might not be > intentional, but > every single patch that gets committed this way is a real > problem > for the project. > > > Phabricato...