dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@free.fr>
To: dri-devel@lists.freedesktop.org
Subject: Re: [Mesa-dev] rules for merging patches to libdrm
Date: Tue, 19 Nov 2013 16:14:38 +0100	[thread overview]
Message-ID: <528B805E.8080800@free.fr> (raw)
In-Reply-To: <528B7E01.4080101@vodafone.de>

Le 19/11/2013 16:04, Christian König a écrit :
> So I think the very first step should be to publish everything on the 
> appropriate lists, and not try an approach like releasing the kernel 
> code first and waiting for it to show up upstream and then try to 
> release the userspace code build on top of it.

Sure, that's why we have private repos and mailing lists.

Steps would be:
- Make a mergeable working prototype you are satisfied with
- Publish all the parts as private repos
- Request for comments and go to step 0 until everyone is satisfied
- Merge it in the kernel, then libdrm, then ddx and mesa

This is pretty much what everyone does already, so I agree with Jerome 
here, No need for a maintainer here as long as people remember that. 
Thanks Dave for spotting this bad behaviour and reminding us of the rule.

Martin

      reply	other threads:[~2013-11-19 15:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 19:29 rules for merging patches to libdrm Dave Airlie
2013-11-08 22:32 ` Matt Turner
2013-11-08 22:59   ` [Mesa-dev] " Kenneth Graunke
2013-11-09  8:11     ` Dave Airlie
2013-11-09 21:26       ` Ian Romanick
2013-11-18 13:29         ` Thierry Reding
2013-11-18 15:17           ` Rob Clark
2013-11-18 15:23             ` [Mesa-dev] " Thierry Reding
2013-11-18 16:21               ` Rob Clark
2013-11-18 16:41                 ` Thierry Reding
2013-11-18 18:38                   ` [Mesa-dev] " Jerome Glisse
2013-11-19  8:18                     ` Thierry Reding
2013-11-18 16:30         ` [Mesa-dev] " Maarten Lankhorst
2013-11-18 16:38           ` Thierry Reding
2013-11-19 14:26   ` Marek Olšák
2013-11-19 15:04     ` [Mesa-dev] " Christian König
2013-11-19 15:14       ` Martin Peres [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=528B805E.8080800@free.fr \
    --to=martin.peres@free.fr \
    --cc=dri-devel@lists.freedesktop.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