public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, pbonzini@redhat.com, lvivier@redhat.com,
	thuth@redhat.com
Subject: [PATCH kvm-unit-tests] Add git.orderFile
Date: Thu,  8 Dec 2016 16:39:19 +0100	[thread overview]
Message-ID: <20161208153919.29773-1-drjones@redhat.com> (raw)

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!
---
 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.
+The orderFile we use is scripts/git.orderfile. Adding the diff.orderFile
+config (git config diff.orderFile scripts/git.orderfile) will enable it.
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
-- 
2.9.3


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 15:39 Andrew Jones [this message]
2016-12-08 18:18 ` [PATCH kvm-unit-tests] Add git.orderFile Radim Krčmář
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=20161208153919.29773-1-drjones@redhat.com \
    --to=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@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