All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm (utils)
Date: Wed, 07 Jun 2006 22:12:43 +0200	[thread overview]
Message-ID: <1149711163.22472.47.camel@localhost> (raw)
In-Reply-To: <loom.20060607T182956-173@post.gmane.org>

Hi Robert,

> After reading some of the other posts I came to find out that diff -u is the
> preferred format.  This is using utils/rfcomm/main.c v 1.18 from the CVS 
> repository.

the context diffs are not really readable by any humans. However please
attach this patch, because your mail client converted all tabs into
whitespaces.

Regards

Marcel




_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-06-07 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07  0:35 [Bluez-devel] rfcomm (utils) Robert Wlaschin
2006-06-07  7:13 ` Marcel Holtmann
2006-06-07 16:36   ` Robert Wlaschin
2006-06-07 20:12     ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-07 15:12 Robert Wlaschin

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=1149711163.22472.47.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.