similar to: [LLVMdev] Bikeshedding commit message policy - Round 3 - Fight!

On 15 March 2015 at 15:06, Hal Finkel <hfinkel at anl.gov> wrote: > I used to use CSE:, but have now switched to using [CSE] because that seems to be the prevailing convention (and is somewhat more visually distinctive). I think it makes sense to codify that convention, but not to require them. Sometimes, there is nothing appropriate to use. Sometimes, the first or second word of the

On 15 March 2015 at 20:22, Chris Lattner <clattner at apple.com> wrote: > Can you post the entire revised diff that you want to include? Is it Diff 21913 on Phab? If so, LGTM. Hi Chris, Here's the final version: http://reviews.llvm.org/D8197 cheers, --renato

On 15 March 2015 at 16:31, Hal Finkel <hfinkel at anl.gov> wrote: > I don't want to code when to use them. But it makes sense to say, "If you want to include a title tag, do it like this...". I'm ok with that. So, do we have consensus? 1. Don't require, but recommend using [] for tags. 2. Don't specify attribution more than just "patch by Foo." and

I have ubuntu 7.10 for a 64 bit pc and i have no clue how to download wine so please please please help me [Exclamation] [Exclamation] [Exclamation]

_History_ I have 100% success in Xen VGA Passthrough with Xen 3.5-unstable with my first Palit NVIDIA Geforce 8400 GS VGA card in 2009, which is 3 years ago. Then my first Palit NVIDIA Geforce 8400 GS VGA card overheated and malfunctioned. So I bought a 2nd Palit NVIDIA Geforce 8400 GS VGA card several months ago in March 2012 for S$44, to replace the first card. At that point in time, Xen

_History_ I have 100% success in Xen VGA Passthrough with Xen 3.5-unstable with my first Palit NVIDIA Geforce 8400 GS VGA card in 2009, which is 3 years ago. Then my first Palit NVIDIA Geforce 8400 GS VGA card overheated and malfunctioned. So I bought a 2nd Palit NVIDIA Geforce 8400 GS VGA card several months ago in March 2012 for S$44, to replace the first card. At that point in time, Xen

Hello. I''m trying to get the lastest GPLPV binary (rev 238) working on an Ubuntu Server host with Xen 4, but I''ve got some problems. The guest is a 64 bit Windows 2008 R2. After enabling test mode and rebooting, installing and rebooting again (with /NOGPLPV) I can see all the Xen devices, but two (out of three) Xen Block Device Driver have an exclamation mark; I don''t

I use ubuntu 9.04 + wine latest version. after I install camfrog by wine. then I try to run it. I can IM with person, but I can't enter to chatroom. After I try to enter into chatroom, program is close. [Exclamation] [Exclamation]

My Asterisk server is behind a NAT and I have set: ---------------------------------------------------------------------------- externhost="my.server.address" externrefresh=180 localnet=192.168.0.0/255.255.0.0 localnet=10.0.0.0/255.0.0.0 localnet=172.16.0.0/12 nat=yes --------------------------------------------------------------------------- in [general] section of sip.conf. I can

Hello All: I'm having a strange issue with the yum proxy settings. It is directly related to passwords containing exclamation points. For example, the following works fine in yum.conf: http_proxy=http://somentlmproxy.somecompany.com http_password=regularpassword However, if the password contains any exclamation points, it will not authenticate properly. E.g., a password such as

> The errors you posted were from the client. Assuming you can ssh into > the remote machine without a problem, do you see error messages there > on the server? Thanks, Akemi, you have hit the nail on the head! The spurious error message was caused by a statement in .cshrc that created output, a stray unescaped exclamation mark in an alias definition. And that with me preaching to my

Hello list; I´ve updated my windows 2k3 GPLPV drivers from 0.9.9 to 0.9.12-pre13. But now, i have two xen block devices; (of course, one of them is not working and is marked with the yellow exclamation). How can i fix it, or how can i uninstall the GPLPV drivers in order to make a clean install? Thanks Juan Pablo _______________________________________________ Xen-users mailing list

We use Microsoft Outlook heavy at school but our backed is CentOS. I use echo "Foo" | mail -s "subject" addr at unc.edu a lot. Is it possible to change the priority to High so Outlook will understand it? The priority meaning the email will be sent to the normal email queue but on Outlook it would have the exclamation point. TIA

Hi, I would like to add a new directive to FileCheck called CHECK-FOO (where FOO is a name under discussion right now) which is used to improve error messages. The idea is that you would use CHECK-FOO on any line that contains a unique identifier (typically labels, function definitions, etc.) that is guaranteed to only occur once in the file; FileCheck will then conceptually break the break the

I have experienced a couple of (minor) problems with Samba Thought I would report these and ask if they are known problems. 1. Problem with "!" in username map file 2. Samba tools e.g. smbstatus, testparm not accounting for "config file" parameter 1. There appears to be a problem with a minor part of username map file interpretation. When I put an exclamation mark

Dear R List I have a small problem concerning the output of print(). My version: > R.version _ platform i386-portbld-freebsd5.2 arch i386 os freebsd5.2 system i386, freebsd5.2 status major 1 minor 9.0 year 2004 month 04 day 12 language R Consider this: I want to print a backslash with an exclamation mark. Here is the output. > print( "\!"

On Wed, Sep 24, 2014 at 4:49 PM, Reid Kleckner <rnk at google.com> wrote: > +1 for a having a short leading sentence followed by a blank line. This is > always the email subject, so plan accordingly. > > IMO the rest doesn't matter and isn't worth codifying. > IMO, none of this is worth codifying really... We could certainly have a little guide for how to write

Hi! Jens Seidel reported a bug to Debian about a wrong message on brctl, you can see it at http://bugs.debian.org/383938, it is kind of the continuation of the ENODEV bug #348617 that was already patched by Stephen on the git. I have applied the same solution that Stephen applied for the first one, follows the patch against git plus a minor exclamation mark modification I did so that all ENODEV

Try putting !!! (three exclamation symbols) in front of which(...)==.... The non-standard evaluation in the tidyverse can cause confusion. Bill Dunlap TIBCO Software wdunlap tibco.com On Thu, Aug 24, 2017 at 4:32 AM, Eugeny Melamud < Eugeny.Melamud at lanit-tercom.com> wrote: > Hi all! > > The following code (executed in console)... > somevar <- data.frame(v1 = 1:5,

I agree with David's sentiment. The second method appears to be easier to follow. IMHO, this would be easier for external users that desire to modify the backend for their own custom extensions/instructions. On Fri, Aug 18, 2017 at 5:05 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk > wrote: > On 18 Aug 2017, at 10:55, Alex Bradbury <asb at asbradbury.org> wrote: >