linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Steve Langasek <steve.langasek@canonical.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/1] Update tests to be compatible with gi and python3
Date: Fri, 15 Jun 2012 13:13:59 +0300	[thread overview]
Message-ID: <20120615101359.GA6586@x220.ger.corp.intel.com> (raw)
In-Reply-To: <20120530075503.GI6539@x220>

Hi Steve,

> On Thu, May 24, 2012, Steve Langasek wrote:
> > From: Steve Langasek <steve.langasek@canonical.com>
> > 
> > This patch makes the python tests source-compatible with python 3, while
> > leaving the interpreter at python 2 for now.
> > 
> > The tradeoff is that this source is no longer compatible with python
> > versions < 2.6, and requires gobject-introspection for the glib-based tests.
> > 
> > Signed-off-by: Steve Langasek <steve.langasek@canonical.com>
> 
> We don't use signed-off-by for user space patches so please leave it out
> from the commit message.
> 
> > ---
> >  test/list-devices      |   30 ++++++++++---------
> >  test/monitor-bluetooth |    6 ++--
> >  test/simple-agent      |   41 +++++++++++++------------
> >  test/simple-endpoint   |   12 ++++----
> >  test/simple-service    |    8 +++--
> >  test/test-adapter      |   52 ++++++++++++++++----------------
> >  test/test-attrib       |   52 ++++++++++++++++----------------
> >  test/test-audio        |    8 +++--
> >  test/test-device       |   78 +++++++++++++++++++++++++-----------------------
> >  test/test-discovery    |   16 +++++-----
> >  test/test-health       |   62 +++++++++++++++++++-------------------
> >  test/test-health-sink  |   24 ++++++++-------
> >  test/test-input        |    8 +++--
> >  test/test-manager      |   12 ++++----
> >  test/test-nap          |    8 +++--
> >  test/test-network      |   10 ++++---
> >  test/test-oob          |   34 +++++++++++----------
> >  test/test-proximity    |   14 +++++----
> >  test/test-sap-server   |   64 ++++++++++++++++++++-------------------
> >  test/test-serial       |   10 ++++---
> >  test/test-serial-proxy |    6 ++--
> >  test/test-service      |   14 +++++----
> >  test/test-telephony    |   38 ++++++++++++-----------
> >  test/test-thermometer  |   28 +++++++++--------
> >  24 files changed, 342 insertions(+), 293 deletions(-)
> 
> In general the patch looks ok, but unfortunately it doesn't apply
> cleanly:
> 
> Applying: Update tests to be compatible with gi and python3
> /home/jh/src/bluez/.git/rebase-apply/patch:838: trailing whitespace.
>  
> /home/jh/src/bluez/.git/rebase-apply/patch:840: trailing whitespace.
>  
> fatal: 2 lines add whitespace errors.
> Patch failed at 0001 Update tests to be compatible with gi and python3
> 
> Please fix this and resend. For the future you might want to add the
> following to your gitconfig:
> 
> [apply]
>         whitespace = error

Since I haven't heard anything from you I went a head and fixed these
issues for you and applied the patch.

Johan

  reply	other threads:[~2012-06-15 10:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25  5:44 [PATCH 1/1] Update tests to be compatible with gi and python3 Steve Langasek
2012-05-30  7:55 ` Johan Hedberg
2012-06-15 10:13   ` Johan Hedberg [this message]
2012-06-15 13:14     ` Lucas De Marchi

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=20120615101359.GA6586@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=steve.langasek@canonical.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).