public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, lvivier@redhat.com,
	thuth@redhat.com
Subject: Re: [PATCH kvm-unit-tests] Add git.orderFile
Date: Thu, 8 Dec 2016 19:18:03 +0100	[thread overview]
Message-ID: <20161208181803.GA29024@potion> (raw)
In-Reply-To: <20161208153919.29773-1-drjones@redhat.com>

2016-12-08 16:39+0100, Andrew Jones:
> It's helpful to have a standard sequence of file types in patches.
> Applying git-diff's orderFile feature allows us to do that. Just
> do 'git config diff.orderFile scripts/git.orderfile' to enable it.
> 
> Signed-off-by: Andrew Jones <drjones@redhat.com>
> ---
> This was inspired by Laszlo's patch for QEMU. Anyway it's high time
> somebody posts some good kvm-unit-tests bikeshedding bait!

I raise 10 hours of our lives!

> ---
>  README                |  4 ++++
>  scripts/git.orderfile | 15 +++++++++++++++
>  2 files changed, 19 insertions(+)
>  create mode 100644 scripts/git.orderfile
> 
> diff --git a/README b/README
> index f8f196d90bf1..73fdd526aed7 100644
> --- a/README
> +++ b/README
> @@ -66,3 +66,7 @@ You can add the following to .git/config to do this automatically for you:
>  [format]
>  	subjectprefix = kvm-unit-tests PATCH
>  
> +Additionally it's helpful to have a standard sequence of file types in
> +patches. Applying git-diff's orderFile feature allows us to do that.

We already have a standard sequence -- alphabetic order. ;)

I assume the goal is to move the abstract parts to the top of the patch
and minute detail to the bottom, allowing reviewers to understand few
more things on the first read.

> +The orderFile we use is scripts/git.orderfile. Adding the diff.orderFile
> +config (git config diff.orderFile scripts/git.orderfile) will enable it.

The only thing we don't want to be changing afterwards is the file path.

What about scripts/git.order?
The file suffix is pretty obvious and other similar git files don't use
file suffix.  e.g. core.excludeFile -> .gitignore and
core.attributesFile -> .gitattributes.

> diff --git a/scripts/git.orderfile b/scripts/git.orderfile
> new file mode 100644
> index 000000000000..b98a0e78a37e
> --- /dev/null
> +++ b/scripts/git.orderfile
> @@ -0,0 +1,15 @@
> +COPYRIGHT
> +MAINTAINERS
> +*README
> +configure
> +*Makefile*
> +*.mak
> +*.py
> +*.bash
> +*/run
> +*.sh
> +*.cfg
> +*.lds
> +*.h
> +*.S
> +*.c

Let's treat lib/ specially, so the lib/ <-> $arch/ order of hunks
remains the same on all arches.

Whew, this bikeshedding stuff is good ... I plan to apply on Monday, to
let other people have some fun as well.

Thanks.

  reply	other threads:[~2016-12-08 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 15:39 [PATCH kvm-unit-tests] Add git.orderFile Andrew Jones
2016-12-08 18:18 ` Radim Krčmář [this message]
2016-12-09  8:15   ` Andrew Jones

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=20161208181803.GA29024@potion \
    --to=rkrcmar@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=thuth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox