All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2]: mcelog module initial rewrite
Date: Tue, 07 Aug 2012 20:10:13 +0200	[thread overview]
Message-ID: <50215A05.60700@trentalancia.com> (raw)
In-Reply-To: <5021550C.7060608@tresys.com>

Hello Christopher.

On 07/08/2012 19:49, Christopher J. PeBenito wrote:
> On 08/06/12 09:46, Dominick Grift wrote:
>>
>>>>
>>>> On Mon, 2012-08-06 at 14:45 +0200, Guido Trentalancia wrote:
>>
>> <..snip ..>
>>
>> Also don't create patches on patches ( i think your v2 patch is a patch
>> on your initial patch?)
>
> I'm still sorting through all the emails, but if thats the case, Guido, please resubmit as a proper patch set (no patches on patches).

It's not patches on patches: they are all the same patch in different 
versions.

Increasing version numbers imply increased stability, improved style and 
so on. But it was mostly working since the initial version, which 
creates an advantage in terms of time, I suppose, if you consider the 
actual state is basically unsupported (daemon won't start).

Since Dominick is not entirely happy with it, I suggest you apply the 
latest version (v4) and then let him follow on, as I am entirely 
satisfied with such version and at the same time I believe I have 
followed all of his advice as applicable (except from the booleans that 
I need on my system).

Regards,

Guido

  reply	other threads:[~2012-08-07 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 12:45 [refpolicy] [PATCH v2]: mcelog module initial rewrite Guido Trentalancia
2012-08-06 13:40 ` Dominick Grift
2012-08-06 13:42   ` Dominick Grift
2012-08-06 13:46     ` Dominick Grift
2012-08-07 17:49       ` Christopher J. PeBenito
2012-08-07 18:10         ` Guido Trentalancia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-06 14:49 Guido Trentalancia
2012-08-06 14:56 ` Dominick Grift
2012-08-06 15:19 Guido Trentalancia
2012-08-06 15:30 ` Dominick Grift

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50215A05.60700@trentalancia.com \
    --to=guido@trentalancia.com \
    --cc=refpolicy@oss.tresys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.