All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	DRI <dri-devel@lists.freedesktop.org>
Subject: Re: [pull] radeon and amdgpu drm-fixes-4.2
Date: Wed, 12 Aug 2015 15:10:49 -0400	[thread overview]
Message-ID: <CADnq5_O4xZLpO=5PmeETRxCSedCB1z6rRd5-=FQA9exetY5cPQ@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFyU8Wj6XQLy647zdxx44kxDVUa+SCsFq7jna51EQKyj_A@mail.gmail.com>

On Wed, Aug 12, 2015 at 2:52 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Wed, Aug 12, 2015 at 10:46 AM, Alex Deucher <alexdeucher@gmail.com> wrote:
>>
>> Dave is on vacation at the moment, so please pull these fixes directly.
>> Just a few minor things for 4.2:
>
> So I've pulled this, but I'm noticing a very alarming pattern in your
> pull requests: the commits are clearly generated just before the
> request, and have presumably had basically no testing at all. S
>
> Gaah. I should have marked some of my longer emails on best git
> practices. Maybe somebody else bookmarked them>
>
> Are you constantly rebasing? If so, why?
>
> I presume that this is your normal behavior, and it's just that Dave
> has never tried to correct that workflow. I've written about a million
> emails about proper git flow, so I'm only exposed to this directly now
> that Dave is on vacation. I notice that the whole "commits generated
> just before pull request" seems to have been true for the last pull
> request too (tip of your tree: Wed Aug 5 14:26:50 2015, email asking
> me to pull: Wed,  5 Aug 2015 16:42:21).
>
> Maybe these commits had testing somewhere else. It's definitely not
> obvious from the pull requests and the git history, though.

I always rebase my pull requests against Dave's drm-fixes tree before
I send a pull request.  Since he's out of town I rebased against your
tree.  I didn't realize that was not the preferred model.  I thought
it was preferred to fix up any possible conflicts that may arise from
other changes in the subsystem tree (although are pretty unlikely).

Alex
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-08-12 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 17:46 [pull] radeon and amdgpu drm-fixes-4.2 Alex Deucher
2015-08-12 18:52 ` Linus Torvalds
2015-08-12 19:10   ` Alex Deucher [this message]
2015-08-12 19:35     ` Linus Torvalds
2015-08-12 19:41       ` Alex Deucher
2015-08-12 19:45       ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2015-07-16 20:58 Alex Deucher
2015-07-09 15:50 Alex Deucher

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='CADnq5_O4xZLpO=5PmeETRxCSedCB1z6rRd5-=FQA9exetY5cPQ@mail.gmail.com' \
    --to=alexdeucher@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=torvalds@linux-foundation.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 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.