From: Michael Ellerman <mpe@ellerman.id.au>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/powerpc: Add .gitignore for powerpc selftests
Date: Wed, 14 Jan 2015 13:15:59 +1100 [thread overview]
Message-ID: <1421201759.10748.8.camel@ellerman.id.au> (raw)
In-Reply-To: <54B5B561.40406@osg.samsung.com>
On Tue, 2015-01-13 at 17:16 -0700, Shuah Khan wrote:
> Please add a commit log.
What does it need to say?
> On 01/13/2015 04:49 PM, Michael Ellerman wrote:
> > Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> > ---
> > .../testing/selftests/powerpc/copyloops/.gitignore | 4 ++++
> > tools/testing/selftests/powerpc/mm/.gitignore | 1 +
> > tools/testing/selftests/powerpc/pmu/.gitignore | 3 +++
> > tools/testing/selftests/powerpc/pmu/ebb/.gitignore | 22 ++++++++++++++++++++++
> > .../selftests/powerpc/primitives/.gitignore | 1 +
> > tools/testing/selftests/powerpc/tm/.gitignore | 1 +
> > 6 files changed, 32 insertions(+)
> > create mode 100644 tools/testing/selftests/powerpc/copyloops/.gitignore
> > create mode 100644 tools/testing/selftests/powerpc/mm/.gitignore
> > create mode 100644 tools/testing/selftests/powerpc/pmu/.gitignore
> > create mode 100644 tools/testing/selftests/powerpc/pmu/ebb/.gitignore
> > create mode 100644 tools/testing/selftests/powerpc/primitives/.gitignore
> > create mode 100644 tools/testing/selftests/powerpc/tm/.gitignore
>
> Please create a single .gitignore for all targets right under
> tools/testing/selftests/powerpc instead of multiple .gitignore
> files.
Why? Having separate files makes it less likely we'll get merge conflicts
between different test subdirectores, it also makes it more likely someone
adding a test will notice they need to update the .gitignore in the same
directory.
cheers
next prev parent reply other threads:[~2015-01-14 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 23:49 [PATCH] selftests/powerpc: Add .gitignore for powerpc selftests Michael Ellerman
2015-01-14 0:16 ` Shuah Khan
2015-01-14 2:15 ` Michael Ellerman [this message]
2015-01-14 3:50 ` Anshuman Khandual
2015-01-14 17:20 ` Shuah Khan
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=1421201759.10748.8.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=shuahkh@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).