From: Jani Nikula <jani.nikula@linux.intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: Gabriel Krisman Bertazi <krisman@collabora.co.uk>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm: qxl: Drop misleading comment
Date: Tue, 31 Jan 2017 11:46:53 +0200 [thread overview]
Message-ID: <87fujzh88i.fsf@intel.com> (raw)
In-Reply-To: <1485852946.23903.29.camel@redhat.com>
On Tue, 31 Jan 2017, Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi,
>
>> branches. One part that imo really should stick around is the drm-tip
>> integration tree rebuilding. That allows us to distribute conflict
>> handling (e.g. between drm-misc-fixes and drm-misc-next), and with more
>> people and more drivers in drm-misc I expect more conflicts.
>
> Ok, good point. I see there is a separate "dim rebuild-top" command, so
> that should be doable no matter how I actually apply the patches.
>
> Trying to run dim throws errors at me though:
>
> kraxel@nilsson ~/tmp/maintainer-tools (maintainer-tools)# ./dim help
> ./dim: line 1602: declare: -n: invalid option
> declare: usage: declare [-aAfFgilrtux] [-p] [name[=value] ...]
> kraxel@nilsson ~/tmp/maintainer-tools (maintainer-tools)# bash --version
> GNU bash, version 4.2.46(1)-release (x86_64-redhat-linux-gnu)
declare -n introduced in bash 4.3 is needed for alias
support. Workaround at [1].
[1] https://lists.freedesktop.org/archives/intel-gfx/2017-January/118474.html
>> But dim apply-branch is a supposed to be a drop-in replacement for git
>> apply-mbox, so should be simple to integrate into another set of scripts
>> to manage the mails. And if there's changes to dim needed to make that
>> happen, we can do that (we push patches to it at a regular pace).
>
> The patches tool prepares a mbox file, then runs "git am". Shouldn't be
> that hard to make it configurable ...
N.b. dim currently doesn't do all its magic, such as adding Link: tag,
if you apply more than one patch at a time. If you apply a multi-patch
mbox, only the last one will get the Link: tag.
BR,
Jani.
>> > Ok. How quickly could I start using drm-misc? I have some pending
>> > patches for the 4.11 merge window. Any chance I can push them through
>> > drm-misc-next? Or should I better send a pull req to Dave?
>>
>> If you want you can get started right away. I plan to type some small docs
>> for this experiment, but the only thing you need is an fdo account with
>> drm-misc commit rights. Simplest to ping me (and fdo admins) on
>> #dri-devel.
>
> Ok.
>
> cheers,
> Gerd
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-31 9:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 1:05 [PATCH 1/4] drm: qxl: Drop misleading comment Gabriel Krisman Bertazi
2017-01-27 1:05 ` [PATCH 2/4] drm: qxl: Drop duplicated device pointer attribute Gabriel Krisman Bertazi
2017-01-27 1:23 ` Emil Velikov
2017-01-27 1:24 ` Emil Velikov
2017-01-27 1:05 ` [PATCH 3/4] drm: qxl: Drop duplicated pci_device " Gabriel Krisman Bertazi
2017-01-27 1:05 ` [PATCH 4/4] drm: qxl: Embed drm_device into driver structure Gabriel Krisman Bertazi
2017-01-27 7:35 ` [PATCH 1/4] drm: qxl: Drop misleading comment Daniel Vetter
2017-01-27 7:37 ` Daniel Vetter
2017-01-27 8:20 ` Gerd Hoffmann
2017-01-27 13:53 ` Daniel Vetter
2017-01-27 16:41 ` Gabriel Krisman Bertazi
2017-01-30 8:17 ` Gerd Hoffmann
2017-01-30 8:27 ` Daniel Vetter
2017-01-30 9:41 ` Gerd Hoffmann
2017-01-30 9:52 ` Daniel Vetter
2017-01-30 17:14 ` Gerd Hoffmann
2017-01-31 7:58 ` Daniel Vetter
2017-01-31 8:55 ` Gerd Hoffmann
2017-01-31 9:04 ` Daniel Vetter
2017-01-31 9:46 ` Jani Nikula [this message]
2017-01-31 10:19 ` Gerd Hoffmann
2017-01-31 11:28 ` Jani Nikula
2017-01-31 16:41 ` Gerd Hoffmann
2017-01-31 16:30 ` Gerd Hoffmann
2017-01-31 17:07 ` Gabriel Krisman Bertazi
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=87fujzh88i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=krisman@collabora.co.uk \
/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.