15.09.2015 19:22, Markus Armbruster wrote:
> "Daniel P. Berrange" writes:
[]
>> Personally I be fine with both the minimal approach or the more
>> comprehensive approach of Peter's, but I'd probably tend towards
>> the minimal approach to avoid the warnings problem.
>
> Seconded.
>
> The "minima
"Daniel P. Berrange" writes:
> On Tue, Sep 15, 2015 at 09:31:08AM -0600, Eric Blake wrote:
>> ping
>>
>> On 08/24/2015 06:15 PM, John Snow wrote:
>> >
>> >
>> > On 06/18/2015 10:05 AM, Markus Armbruster wrote:
>> >> Peter Maydell writes:
>> >>
>> >>> On 18 June 2015 at 10:28, Markus Armbruste
On Tue, Sep 15, 2015 at 09:31:08AM -0600, Eric Blake wrote:
> ping
>
> On 08/24/2015 06:15 PM, John Snow wrote:
> >
> >
> > On 06/18/2015 10:05 AM, Markus Armbruster wrote:
> >> Peter Maydell writes:
> >>
> >>> On 18 June 2015 at 10:28, Markus Armbruster wrote:
> However, I can't see how
ping
On 08/24/2015 06:15 PM, John Snow wrote:
>
>
> On 06/18/2015 10:05 AM, Markus Armbruster wrote:
>> Peter Maydell writes:
>>
>>> On 18 June 2015 at 10:28, Markus Armbruster wrote:
However, I can't see how I could define a new C style there without
pushing the "local variables" fe
On 06/18/2015 10:05 AM, Markus Armbruster wrote:
> Peter Maydell writes:
>
>> On 18 June 2015 at 10:28, Markus Armbruster wrote:
>>> However, I can't see how I could define a new C style there without
>>> pushing the "local variables" feature well beyond its intended use, and
>>> triggering th
Peter Maydell writes:
> On 18 June 2015 at 10:28, Markus Armbruster wrote:
>> However, I can't see how I could define a new C style there without
>> pushing the "local variables" feature well beyond its intended use, and
>> triggering the confirmation prompts.
>
> We wouldn't want to define a ne
On 18 June 2015 at 10:28, Markus Armbruster wrote:
> However, I can't see how I could define a new C style there without
> pushing the "local variables" feature well beyond its intended use, and
> triggering the confirmation prompts.
We wouldn't want to define a new C style, but in general the it
Peter Maydell writes:
> On 4 June 2015 at 14:30, Daniel P. Berrange wrote:
>> Some default emacs setups indent by 2 spaces and uses tabs
>> which is counter to the QEMU coding style rules. Adding a
>> .dir-locals.el file in the top level of the GIT repo will
>> inform emacs about the QEMU coding
On Thu, Jun 04, 2015 at 02:41:42PM +0100, Peter Maydell wrote:
> On 4 June 2015 at 14:30, Daniel P. Berrange wrote:
> > Some default emacs setups indent by 2 spaces and uses tabs
> > which is counter to the QEMU coding style rules. Adding a
> > .dir-locals.el file in the top level of the GIT repo
On 4 June 2015 at 14:30, Daniel P. Berrange wrote:
> Some default emacs setups indent by 2 spaces and uses tabs
> which is counter to the QEMU coding style rules. Adding a
> .dir-locals.el file in the top level of the GIT repo will
> inform emacs about the QEMU coding style, and so assist
> contri
Some default emacs setups indent by 2 spaces and uses tabs
which is counter to the QEMU coding style rules. Adding a
.dir-locals.el file in the top level of the GIT repo will
inform emacs about the QEMU coding style, and so assist
contributors in avoiding common style mistakes before
they submit pa
11 matches
Mail list logo
