From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rob Clark <robdclark@gmail.com>, John Hunter <zhjwpku@gmail.com>
Cc: John Hunter <zhaojunwang@pku.edu.cn>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm_crtc.c: fix some typo mistake and some annotations mistake
Date: Fri, 13 Mar 2015 14:34:39 +0200 [thread overview]
Message-ID: <877fulqdnk.fsf@intel.com> (raw)
In-Reply-To: <CAF6AEGsL+sepAJTa6PP2Ujm7HRdyWN3CnqJdGbxmrgf6_vNrig@mail.gmail.com>
On Fri, 13 Mar 2015, Rob Clark <robdclark@gmail.com> wrote:
> hopefully someone else in China can suggest a good way of sending
> patches (I have no clue there)
An alternative is to subscribe with all email addresses you may be
sending patches (or messages) from, but disabling list mail delivery for
all but one address in the dri-devel list management interface.
You can have git format-patch/send-email add a From: line at the
beginning of the patch (separate from mail headers) matching the
Signed-off-by. I forget the config for this, but it's there somewhere.
HTH,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-03-13 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 8:02 [PATCH] drm_crtc.c: fix some typo mistake and some annotations mistake John Hunter
2015-03-12 14:15 ` John Hunter
2015-03-12 14:34 ` Rob Clark
2015-03-13 0:49 ` John Hunter
2015-03-13 1:16 ` Rob Clark
2015-03-13 12:34 ` Jani Nikula [this message]
2015-03-14 2:02 ` John Hunter
2015-03-13 2:33 ` Rob Clark
2015-03-13 2:53 ` John Hunter
2015-03-13 3:07 ` Rob Clark
2015-03-13 3:31 ` John Hunter
2015-03-13 3:34 ` Rob Clark
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=877fulqdnk.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.com \
--cc=zhaojunwang@pku.edu.cn \
--cc=zhjwpku@gmail.com \
/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.