From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Updated sendto
Date: Mon, 25 Feb 2008 10:56:37 +0000 [thread overview]
Message-ID: <1203936997.2754.198.camel@cookie.hadess.net> (raw)
In-Reply-To: <EB2E724A-6D73-4349-B937-7935A8C4BEFB@holtmann.org>
On Mon, 2008-02-25 at 03:21 +0100, Marcel Holtmann wrote:
> Hi Bastien,
>
> >>>
> >>> And one that works with obex-data-server 0.1
> >>
> >> Updated against current CVS, and fix a memleak when getting the
> >> adapters
> >> list. New main.c file attached as well, for easier review.
> >
> > Updated against current CVS.
>
> I've been through the main.c as whole and the actual patch. As you
> saw, I took the dialogs out of it since that made sense and was a sane
> way to do it. I mentioned that I want small patches and if they are
> small and logical, I apply them most of the times immediately. Smaller
> patches are easier to review. I am not taking a big chunk blindly.
>
> So current patch is not acceptable. It is actually bad. So first
> action must be to remove all these useless comments. An example is this:
>
> + /* Go into main loop */
> gtk_main();
>
> Put comments where the code is unclear and not were everybody knows
> what it is doing. This is a perfect example of wrongly commenting code.
Done locally.
> Second of all, I am unhappy with all this usage of gtk_main_quit() in
> various functions. Can we not just structure the code a lot more
> cleaner to avoid multiple calls of it.
I don't understand what you mean there.
> Besides the signal handling, I
> would expect one extra call in case we automatically wanna close the
> progress dialog.
Why? If there's no errors, why would you want to see it's finished? What
information would be in the dialogue that could be useful?
-------------------------------------------------------------------------
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-02-25 10:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 10:43 [Bluez-devel] [PATCH] Allow multiple files to be sent Bastien Nocera
2008-01-18 13:43 ` Bastien Nocera
2008-02-01 13:14 ` Bastien Nocera
2008-02-01 16:08 ` Bastien Nocera
2008-02-01 16:20 ` Bastien Nocera
2008-02-06 12:18 ` [Bluez-devel] [PATCH] Updated sendto Bastien Nocera
2008-02-06 13:08 ` Bastien Nocera
2008-02-07 0:59 ` Bastien Nocera
2008-02-23 1:30 ` Bastien Nocera
2008-02-24 18:29 ` Bastien Nocera
2008-02-25 2:21 ` Marcel Holtmann
2008-02-25 10:56 ` Bastien Nocera [this message]
2008-02-25 20:36 ` Marcel Holtmann
2008-02-26 1:18 ` Bastien Nocera
2008-02-26 1:21 ` Marcel Holtmann
2008-02-27 1:28 ` Bastien Nocera
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=1203936997.2754.198.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--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