From: nitin.a.kamble@intel.com
To: Openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Misc: detect trailing space in the patches
Date: Wed, 5 Dec 2012 15:37:40 -0800 [thread overview]
Message-ID: <cover.1354750505.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
This commit is for detecting trailing white space in the create-pull-request script.
Thanks,
Nitin
The following changes since commit 381c4b69c7e8b452f4d3de2f8214e6e5f6a9abe7:
sstate.bbclass: fix detection of owners matching sstate files (2012-12-05 15:34:07 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/misc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
Nitin A Kamble (1):
create-pull-request: detect trailing white space
scripts/create-pull-request | 13 ++++++++++++-
1 files changed, 12 insertions(+), 1 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-12-05 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 23:37 nitin.a.kamble [this message]
2012-12-05 23:37 ` [PATCH 1/1] create-pull-request: detect trailing white space nitin.a.kamble
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=cover.1354750505.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=Openembedded-core@lists.openembedded.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