mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Konstantin Ryabitsev <mricon@kernel.org>,
	"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: Expressing linux-next collateral evolutions in formal grammar
Date: Fri, 2 Nov 2012 10:48:30 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1211021045200.2014@localhost6.localdomain6> (raw)
In-Reply-To: <CAB=NE6Xv5Lag0J2U3CHK9huzMQLyJEZmdrcqWWomn48w=xUnag@mail.gmail.com>

> The way I would envision this to be easier to manage is to break them
> down by subsystem and the reviewer can then go and read the grammar
> for their own subsystem of preference. The long term benefit of this
> is that even if folks don't use SmPL for collateral evolutions we have
> a possibility here of being able to backport a collateral evolution by
> using the inverse of the SmPL grammar, if we can get to the point of
> coming up with formal and proper grammar on each collateral evolution.
>
> Thoughts?

I had liked the idea of lwn, because that makes it public but doesn't 
bother anyone.  But another option would be to just send an email to the 
relevant maintainer?  Perhaps it would be better to send the email just 
to the specific maintainer for the file, and not all the way up the 
maintainer hierarchy, because these would be just suggestions of things to 
look at, and not actual patch proposals.

thanks,
julia

      reply	other threads:[~2012-11-02  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  3:09 Luis R. Rodriguez
2012-11-02  9:48 ` Julia Lawall [this message]

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=alpine.DEB.2.02.1211021045200.2014@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=backports@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mricon@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®