From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/edid: Reduce horizontal timings for pixel replicated modes
Date: Fri, 5 Sep 2014 11:08:05 +0300 [thread overview]
Message-ID: <20140905080805.GP4193@intel.com> (raw)
In-Reply-To: <CAKMK7uF=eOhYYQ7Oq0nL2LRYRfZLT+yB-0njB7Ds+HY7cpxMHA@mail.gmail.com>
On Thu, Sep 04, 2014 at 08:31:07PM +0200, Daniel Vetter wrote:
> Readding intel-gfx since this is interesting for everyone.
>
> On Thu, Sep 4, 2014 at 8:09 PM, Clint Taylor <clinton.a.taylor@intel.com> wrote:
> > I will attempt to improve my patch submissions process. I also need to start
> > annotating version in the subject field as well.
> >
> > When using --in_reply_to= do I just use the Message-ID: from the original
> > patch message header or do I use the Message-ID: from the reply asking for
> > the change?
>
> Usually I reply to the previous patch version to avoid threads nesting
> too badly, but other people reply to the last review comment. It
> doesn't really matter.
I tend to do the latter, but I must admit the threads sometimes get
rather messy, so I think I'll change my ways. The changelog in the
patch should anyway keep the story together.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-09-05 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 21:21 [PATCH] drm/edid: Reduce horizontal timings for pixel replicated modes clinton.a.taylor
2014-08-26 8:10 ` Daniel Vetter
2014-08-26 8:11 ` Daniel Vetter
2014-09-01 13:12 ` Ville Syrjälä
2014-09-01 13:17 ` Ville Syrjälä
[not found] ` <5408AAF6.2070300@intel.com>
2014-09-04 18:31 ` Daniel Vetter
2014-09-05 7:03 ` Jani Nikula
2014-09-05 8:08 ` Ville Syrjälä [this message]
2014-09-01 13:19 ` [Intel-gfx] " Ville Syrjälä
-- strict thread matches above, loose matches on Subject: below --
2014-08-18 21:02 clinton.a.taylor
2014-08-14 18:09 clinton.a.taylor
2014-08-14 18:48 ` Ville Syrjälä
2014-08-18 17:29 ` Clint Taylor
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=20140905080805.GP4193@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox