From: Daniel Vetter <daniel@ffwll.ch>
To: jiang.biao2@zte.com.cn
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RESEND PATCH] drm/gma500: Fix comments in gtt.c
Date: Wed, 10 Aug 2016 11:22:14 +0200 [thread overview]
Message-ID: <20160810092214.GS6232@phenom.ffwll.local> (raw)
In-Reply-To: <OF54A77CFE.8216F23B-ON4825800B.002FB89E-4825800B.0030C05C@zte.com.cn>
On Wed, Aug 10, 2016 at 04:52:53PM +0800, jiang.biao2@zte.com.cn wrote:
>
>
> Daniel Vetter <daniel.vetter@ffwll.ch> wrote on 2016/08/10 16:35:29:
>
> > Daniel Vetter <daniel@ffwll.ch>
> > From: Daniel Vetter <daniel.vetter@ffwll.ch>
> >
> > 2016/08/10 16:35
> >
> >
> > jiang.biao2@zte.com.cn,
> >
> >
> > Re: [RESEND PATCH] drm/gma500: Fix comments in gtt.c
> >
> > On Wed, Aug 10, 2016 at 11:35:14AM +0800, jiang.biao2@zte.com.cn wrote:
> > >
> > > Fix some comment faults in gtt.c.
> > >
> > > Signed-off-by: Jiang Biao <jiang.biao2@zte.com.cn>
> >
> > Sending the same patch 3 times in just one hour doesn't help - people
> > sometimes sleep, or are busy. Please let at least a few days pass until
> > you ping (with a reply) or resend.
> >
> > Thanks, Daniel
> >
> I'm so sorry about the interruption.
> The mail server of my company corrupted the format of first two patchs,
> and I have to resend it with correct format, after I corrected the
> configuration of the mail server. The format of the last one should be
> right.
> I'm fresh to this mailing list, next time should be right.
> Thanks a lot.
Ah now worries. In such a case simply add a small comment to your resend
patches why you're resending. You can add such comments to the commit
message at the and after a line with just --- git will then cut it away.
E.g.
... commmit message ...
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
This here is an additional comment which will not get applied to the real
git log.
Making sure that the patch isn't corrupted is definitely appreciated!
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-10 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 3:35 [RESEND PATCH] drm/gma500: Fix comments in gtt.c jiang.biao2
2016-08-10 8:35 ` Daniel Vetter
2016-08-10 8:52 ` jiang.biao2
2016-08-10 9:22 ` Daniel Vetter [this message]
2016-08-11 0:45 ` 答复: " jiang.biao2
-- strict thread matches above, loose matches on Subject: below --
2016-08-10 2:18 jiang.biao2
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=20160810092214.GS6232@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiang.biao2@zte.com.cn \
/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