All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org,
	Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Subject: Re: [PATCH 1/4] drm: qxl: Drop misleading comment
Date: Tue, 31 Jan 2017 13:28:49 +0200	[thread overview]
Message-ID: <87h94f31u6.fsf@intel.com> (raw)
In-Reply-To: <1485857999.23903.60.camel@redhat.com>

On Tue, 31 Jan 2017, Gerd Hoffmann <kraxel@redhat.com> wrote:
>   Hi,
>
>> 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
>
> Works for me.  Thanks.

Thanks, pushed.

>> 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.
>
> Hmm, that is bad.

Agreed.

> One of the things the patches tool actually is very good at is applying
> a patch series.  Grab the patches from the list, put them into a mbox
> file, in the correct order (which is a PITA to do manually with a MUA,
> especially in case there are replies with reviewed-by, ...).

Oh, it's a Notmuch based tool? Cool. I should add that to the Notmuch
wiki.

The notmuch-emacs interface lets you pipe all the open messages in a
thread using "c-u |". So you can expand/collapse messages as you like,
and pipe them all as mbox. But that doesn't work either because dim
can't properly handle it. I have a vested interest to fix this, but I
haven't gotten around to it...

> Does dim detect that a Link: tag is already present and doesn't add
> another one then?

Nope. Patches welcome. ;)

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-01-31 11:28 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
2017-01-31 10:19                     ` Gerd Hoffmann
2017-01-31 11:28                       ` Jani Nikula [this message]
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=87h94f31u6.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --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.