From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: reverend@unrooted.net
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] ussp-push and obextool repackage
Date: 01 Jul 2003 15:14:04 +0200 [thread overview]
Message-ID: <1057065253.15796.37.camel@pegasus> (raw)
In-Reply-To: <1056930669.3eff7b6da605c@www.unrooted.net>
Hi,
> I've gotten a bunch of messages over the last few days about ussp-push, a hack
> which I did a while ago to transfer files over rfcomm links. So if people are
> still using it, I figured I would release a version updated to work with the
> latest openobex library. I've also packaged up the obextool utility that Marcel
> used to have in CVS, hopefully he doesn't mind. IMO, the obextool version is a
> much better tool, but both of them are in the package. Use whichever you like.
> I've espanded the README quite a bit to hopefully answer the questions I hear
> most often. My thanks to those of you who sent me patches for the updates to
> ussp-push. -- Rev
the obextool from CVS is replaced by the btobex program. It can be found
in the CVS module obex.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2003-07-01 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 23:51 [Bluez-users] ussp-push and obextool repackage reverend
2003-07-01 13:14 ` Marcel Holtmann [this message]
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=1057065253.15796.37.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-users@lists.sourceforge.net \
--cc=reverend@unrooted.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox