From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] enable auth and BNEP question?
Date: Fri, 20 Oct 2006 04:36:39 +0200 [thread overview]
Message-ID: <1161311799.27585.8.camel@localhost> (raw)
In-Reply-To: <4537DB32.7080903@flcd.net>
Hi Denis,
> But I've got another a bit off topic and lame question, I've never send
> patches before but would like to help when I can. So if I would find a
> bug and solution for it in future, should I just generate patch in a way
> like this:
> "|diff -up original modified > patch"
> and send it to mail-list or there are some other commonly used procedure?
only make sure it is a unified diff (-u), because I am unable to read
context diffs. I personally to most patches with "cvs diff -u" directly
from the CVS repository.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-10-20 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 15:32 [Bluez-users] enable auth and BNEP question? Denis
2006-09-15 9:51 ` Marcel Holtmann
2006-09-15 16:16 ` Denis
2006-09-15 16:19 ` Marcel Holtmann
2006-09-29 21:57 ` Denis
2006-09-29 22:03 ` Marcel Holtmann
2006-10-19 20:08 ` Denis
2006-10-20 2:36 ` 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=1161311799.27585.8.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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.