All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/8] dim: move -nigthly into drm-nighly.git
Date: Mon, 17 Oct 2016 10:10:39 +0200	[thread overview]
Message-ID: <20161017081039.GG20761@phenom.ffwll.local> (raw)
In-Reply-To: <20161016184810.12030-1-daniel.vetter@ffwll.ch>

On Sun, Oct 16, 2016 at 08:48:02PM +0200, Daniel Vetter wrote:
> Hi all,
> 
> This is the first step to split out the drm-misc trees into their own git repo.
> This just moves the integration trees into drm-nightly.git. Those are separate
> since I really like the idea of sharing one integration tree related to gfx.
> 
> Next up is teaching all the branch related dim commands to figure out the right
> remote. But I think it'd be good to frist roll out this change, actually
> splitting out drm-misc.git will then not affect any of the drm-intel committers.

People asked why on irc, so here's a bit more context: I want to extract
drm-misc into a separate repo for a bunch of reasons. Doing the committer
model for drm-misc within the drm-intel.git repo was really just for a
quick test-drive to see whether it would work. But before scaling it out I
need to fix that:
- separate git repos is the only way to do acls on fd.o
- I want the same model like for drm-intel-next-queued where the main
  branch is always open for drm-misc, with a -next-fixes as needed.
- "eww, intel" reactions from the arm side, so better separation ;-)

Now I still think the shared integration tree is really useful, hence why
I want to keep just one for both trees. Which means step 1 is to first
split out integration tree stuff into a new drm-nightly.git, which both
groups can push to.
-Daniel

> 
> Cheers, Daniel
> 
> Daniel Vetter (8):
>   dim: Extract TODO
>   dim: Autocheck for up-to-dateness
>   dim: autodetect remotes, first part for dim_setup
>   dim: support git worktree for aux checkouts
>   dim: Nuke nightly-forget
>   dim: autodetect branches in rebuild-nightly
>   dim: remove integration-tree remotes
>   dim: Split out drm-nightly.git
> 
>  TODO |  25 ++++++++
>  dim  | 227 +++++++++++++++++++++++++++++++++++--------------------------------
>  qf   |  11 ----
>  3 files changed, 144 insertions(+), 119 deletions(-)
>  create mode 100644 TODO
> 
> -- 
> 2.9.3
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2016-10-17  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-16 18:48 [PATCH 0/8] dim: move -nigthly into drm-nighly.git Daniel Vetter
2016-10-16 18:48 ` [PATCH 1/8] dim: Extract TODO Daniel Vetter
2016-10-16 18:48 ` [PATCH 2/8] dim: Autocheck for up-to-dateness Daniel Vetter
2016-10-16 18:48 ` [PATCH 3/8] dim: autodetect remotes, first part for dim_setup Daniel Vetter
2016-10-16 18:48 ` [PATCH 4/8] dim: support git worktree for aux checkouts Daniel Vetter
2016-10-16 18:48 ` [PATCH 5/8] dim: Nuke nightly-forget Daniel Vetter
2016-10-16 18:48 ` [PATCH 6/8] dim: autodetect branches in rebuild-nightly Daniel Vetter
2016-10-16 18:48 ` [PATCH 7/8] dim: remove integration-tree remotes Daniel Vetter
2016-10-16 18:48 ` [PATCH 8/8] dim: Split out drm-nightly.git Daniel Vetter
2016-10-17  8:10 ` Daniel Vetter [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=20161017081039.GG20761@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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 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.