From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Ignore built files
Date: Wed, 16 Jan 2008 16:32:46 +0100 [thread overview]
Message-ID: <1200497567.7978.51.camel@aeonflux> (raw)
In-Reply-To: <1200489349.26259.29.camel@cookie.hadess.net>
Hi Bastien,
> First "patch" is to add some cvsignore files, cleaning up patches:
> http://bugzilla.gnome.org/attachment.cgi?id=101355&action=view
>
> Just untar in the root directory of the checkout. BZ:
> http://bugzilla.gnome.org/show_bug.cgi?id=504745
I never bothered with the .cvsignore stuff, because the way CVS uses it
is totally stupid and calling "make maintainer-clean" will give you a
complete clean repository.
> I'd need an opinion on another bug:
> http://bugzilla.gnome.org/show_bug.cgi?id=505605
>
> I think that it would be a good idea to move the adapter name to the top
> of the dialogue, as it is rather more important than the mode of
> operation.
Actually I think the mode is more important. You might change your name
once, but the mode change (especially with the visible timeout) is the
one that you use more often.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-01-16 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 13:15 [Bluez-devel] [PATCH] Ignore built files Bastien Nocera
2008-01-16 15:32 ` Marcel Holtmann [this message]
2008-01-16 15:35 ` Bastien Nocera
2008-01-16 15:43 ` Marcel Holtmann
2008-01-16 15:53 ` Bastien Nocera
2008-01-16 19:17 ` Marcel Holtmann
2008-01-16 19:28 ` Bastien Nocera
2008-01-16 19:47 ` Marcel Holtmann
2008-01-16 21:29 ` Jaap A. Haitsma
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=1200497567.7978.51.camel@aeonflux \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox