From: Lukas Wunner <lukas@wunner.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: RFC: late drm pull requests and other topics
Date: Tue, 7 Mar 2017 20:51:15 +0100 [thread overview]
Message-ID: <20170307195115.GA4091@wunner.de> (raw)
In-Reply-To: <CADnq5_N1EZd3mn6yXS91g3ATkcBbCGpTda_c=OHJJApEkDYpCQ@mail.gmail.com>
On Tue, Mar 07, 2017 at 10:56:49AM -0500, Alex Deucher wrote:
> On Mon, Mar 6, 2017 at 7:11 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> I've always tried to have all major new features sent to Dave by rc5,
> so no problems with the timelines. Dave and Linus have generally been
> ok with new asic support at strange times assuming it has minimal
> impact on existing support. Our code release dates rarely line up
> well with kernel cycles, but we can manage.
Well, you were also once the target of a rant because of too recent
commit dates that turned out to have an entirely innocuous explanation:
https://www.spinics.net/lists/dri-devel/msg87996.html
In a follow-up, Linus said "I want to at least be able to fool myself
into thinking that downstream has really worked hard at validating what
they send me".
https://www.spinics.net/lists/dri-devel/msg87999.html
So since he was asking for it, maybe use something like:
GIT_AUTHOR_DATE=`date --date="8 weeks ago"` \
GIT_COMMITTER_DATE=`date --date="4 weeks ago"` \
git commit --amend --date
Best regards ;-)
Lukas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-07 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 0:11 RFC: late drm pull requests and other topics Daniel Vetter
2017-03-07 14:54 ` Sean Paul
2017-03-07 16:51 ` Jani Nikula
2017-03-07 15:56 ` Alex Deucher
2017-03-07 19:51 ` Lukas Wunner [this message]
2017-03-07 20:45 ` Alex Deucher
2017-03-07 16:42 ` Jani Nikula
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=20170307195115.GA4091@wunner.de \
--to=lukas@wunner.de \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).