From: Dave Gordon <david.s.gordon@intel.com>
To: Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [maintainer-tools PATCH] drm-intel: Add note about patches that move code between files
Date: Wed, 9 Mar 2016 12:50:56 +0000 [thread overview]
Message-ID: <56E01C30.7040309@intel.com> (raw)
In-Reply-To: <1457523985-6261-1-git-send-email-ander.conselvan.de.oliveira@intel.com>
On 09/03/16 11:46, Ander Conselvan de Oliveira wrote:
> Patches that move big chunks of code between files can cause some
> complicated conflicts. Add a note to coordinate with maintainers before
> merging such patches.
>
> Signed-off-by: Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@intel.com>
> ---
> drm-intel.rst | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drm-intel.rst b/drm-intel.rst
> index c0c2f20..89df24b 100644
> --- a/drm-intel.rst
> +++ b/drm-intel.rst
> @@ -350,6 +350,10 @@ An inexhaustive list of details to check:
> http://developercertificate.org/. dim apply-branch should do this
> automatically for you.
>
> +* For patches that move around lots of code (file rename or extraction) please
> + coordinate with maintainers to avoid unnecessary pain with conflicts. Usually
> + some explicit merges are needed to avoid git getting lost.
> +
> On Confidence, Complexity, and Transparency
> -------------------------------------------
Perhaps also add a note about "git blame -C", as recently discussed here
by Tvrtko & Arun in the thread "[PATCH 044/190] drm/i915: Move GEM
request routines to i915_gem_request.c"?
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-09 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 11:46 [maintainer-tools PATCH] drm-intel: Add note about patches that move code between files Ander Conselvan de Oliveira
2016-03-09 12:50 ` Dave Gordon [this message]
2016-03-10 8:34 ` Ander Conselvan De Oliveira
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=56E01C30.7040309@intel.com \
--to=david.s.gordon@intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--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