Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][STABLE 1/4] bug20/xorg.conf: update to use tslib driver for touchscreen input device.
Date: Wed, 16 Jun 2010 17:22:53 +0200	[thread overview]
Message-ID: <20100616152253.GD20969@excalibur.local> (raw)
In-Reply-To: <hvapp0$9vs$1@dough.gmane.org>

Hello.

On Wed, 2010-06-16 at 17:14, Koen Kooi wrote:
> 
> On 16-06-10 17:09, Stefan Schmidt wrote:
> > Hello.
> > 
> > On Wed, 2010-06-16 at 11:46, Koen Kooi wrote:
> >>
> >> On 15-06-10 20:15, Stefan Schmidt wrote:
> >>> From: Ken Gilmer <ken@buglabs.net>
> >>>
> >>>
> >>> Signed-off-by: Ken Gilmer <ken@buglabs.net>
> >>> Signed-off-by: Stefan Schmidt <stefan@buglabs.net>
> >>
> >> Acked-by: Koen Kooi <koen@openembedded.org>
> > 
> > Just to make sure I understand the stable process correctly. As this patches
> > don't touch anything in the core system I'm fine apply them to stable myself
> > after fetching them with the ACK form patchwork, right?
> 
> Not quite, you need 2 acks from maintainers of the stable branch (which
> I think includes Marcin, Denys and me).
> But given the low impact of these patches and the general stagnation of
> stable/2009, I think it's safe to apply these.

Hmm, I thought two ACKs are only needed for core changes. At least this is how I
read the part in the wiki:
http://wiki.openembedded.net/index.php/Stable

Types of changes

    * change touches core system (which is anything in tested images or
    * classes/)
    * change touches only machine which you maintain
    * change touches only your distro and and it builds
    * any new stuff which not touch tested stuff 

Changes of first type will require 2 Acks and one of them must be given by one
of stable branch maintainers.

Last type changes are new distros, machines, recipes/classes etc.

I can wait for another ack if that makes people feel better.

regards
Stefan Schmidt



  reply	other threads:[~2010-06-16 15:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 18:15 Extending bug20 support in stable Stefan Schmidt
2010-06-15 18:15 ` [PATCH][STABLE 1/4] bug20/xorg.conf: update to use tslib driver for touchscreen input device Stefan Schmidt
2010-06-16  9:46   ` Koen Kooi
2010-06-16 15:09     ` Stefan Schmidt
2010-06-16 15:14       ` Koen Kooi
2010-06-16 15:22         ` Stefan Schmidt [this message]
2010-06-16 15:25         ` Tom Rini
2010-06-16 15:38           ` Stefan Schmidt
2010-06-16 15:58             ` Marcin Juszkiewicz
2010-06-16 15:53           ` Marcin Juszkiewicz
2010-06-16 15:53   ` Marcin Juszkiewicz
2010-06-15 18:15 ` [PATCH][STABLE 2/4] bug20.conf: Sync with Bug Labs repo Stefan Schmidt
2010-06-16  9:47   ` Koen Kooi
2010-06-16 15:53   ` Marcin Juszkiewicz
2010-06-15 18:15 ` [PATCH][STABLE 3/4] netcat_0.7.1: Gettext is needed Stefan Schmidt
2010-06-15 19:16   ` Tom Rini
2010-06-16  9:47   ` Koen Kooi
2010-06-15 18:15 ` [PATCH][STABLE 4/4] u-boot_git: Add bug20 support Stefan Schmidt
2010-06-16  8:29   ` Jens Seidel
2010-06-16  9:20     ` Stefan Schmidt
2010-06-16 16:36       ` Stefan Schmidt
2010-06-26 15:52         ` Stefan Schmidt

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=20100616152253.GD20969@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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