g_io_channel_win32_new_messages() WaitForSingleObject()

2009-03-31 Thread Thomas Stover
Anyone know if you can use a win32 message io channel on arbitrary handles or just gdi windows or whatever the intended use of that is? I openly admit a don't get windows at all, so this maybe just really out there. Specifically, if I had handle returned from RegisterServiceCtrlHandler()

Re: g_io_channel_win32_new_messages() WaitForSingleObject()

2009-03-31 Thread Tor Lillqvist
Anyone know if you can use a win32 message io channel on arbitrary handles Nope. It is just for window messages for the window indicated by the HWND parameter. Specifically, if I had handle returned from RegisterServiceCtrlHandler() (which as best as I can imagine in my linux centric reality

Re: g_io_channel_win32_new_messages() WaitForSingleObject()

2009-03-31 Thread Thomas Stover
Tor Lillqvist wrote: I have never used that service control API, no idea what it is used for even... oh, just the needlessly complex, 75 step, windows' equivalent to daemon() But if MSDN says that the returned SERVICE_STATUS_HANDLE actually is a normal HANDLE and a waitable one even, that

RE: Cross-compiling GLib 2.18 with arm-linux.

2009-03-31 Thread John Peterson
-Original Message- From: Felipe Contreras [mailto:felipe.contre...@gmail.com] Sent: Friday, March 27, 2009 4:01 AM To: John Peterson Cc: gtk-devel-list@gnome.org Subject: Re: Cross-compiling GLib 2.18 with arm-linux. 2009/3/23 John Peterson j0...@comcast.net: Hello � I�m not sure I�ve

Re: Cross-compiling GLib 2.18 with arm-linux.

2009-03-31 Thread Brian J. Tarricone
On Fri, 27 Mar 2009 13:00:52 +0200 Felipe Contreras wrote: 2009/3/23 John Peterson j0...@comcast.net: Hello – I’m not sure I’ve got the right mailing list for this question, but I thought I’d try. I have downloaded glib-2.18.0 on Linux FC4, and am trying to cross-compile with an

Re: Moving GLib and GTK+ to git

2009-03-31 Thread Kristian Høgsberg
On Mon, 2009-03-30 at 12:47 -0400, Matthias Clasen wrote: Last week, I said that I'd like to get this done by the end of March, which is almost upon us now. Therefore, I'd like to ask everybody to hold off with committing to svn. While we are not quite ready to start the migration yet, it

Re: Moving GLib and GTK+ to git

2009-03-31 Thread Matthias Clasen
I should have also mentioned that the commands you need are: git clone git://git.gnome.org/glib git clone git://git.gnome.org/gtk+ A lot more information about the git migration and git in general can be found at http://live.gnome.org/GitMigration. ___

Re: Moving GLib and GTK+ to git

2009-03-31 Thread Martin Nordholts
Matthias Clasen wrote: - First line (the brief description) must only be one sentence and must not start with a capital letter. Don't use a trailing period either. Don't exceed 76 characters. Hi, Is there any particular reason for not starting with a capital letter, e.g. are there any

Re: Moving GLib and GTK+ to git

2009-03-31 Thread Behdad Esfahbod
On 03/31/2009 03:05 PM, Matthias Clasen wrote: Some things that we need to sort out include ChangeLog: The git way of doing things is to do small commits, with meaningful commit messages, and forego a separate ChangeLog file. Everybody who I talked to about this recommended going this way, so

Re: Moving GLib and GTK+ to git

2009-03-31 Thread David Zeuthen
Hi, On Tue, 2009-03-31 at 21:29 +0200, Martin Nordholts wrote: Matthias Clasen wrote: - First line (the brief description) must only be one sentence and must not start with a capital letter. Don't use a trailing period either. Don't exceed 76 characters. (Btw, should probably say

Re: Moving GLib and GTK+ to git

2009-03-31 Thread Behdad Esfahbod
On 03/31/2009 03:50 PM, David Zeuthen wrote: Personally I prefer non-capital and no periods; it makes the output of 'git log |git shortlog' nicer to look at (see [1] for an example) but maybe that's just me. I think capital letters would work nice here too; trailing periods would probably look

Re: Moving GLib and GTK+ to git

2009-03-31 Thread David Zeuthen
On Tue, 2009-03-31 at 15:05 -0400, Matthias Clasen wrote: Commit messages: Here are some recommendations that I think meet our needs: It would be nice to have hooks to enforce this in the master repo at git.gnome.org. Thoughts? Working with branches: As Kristian explained to me, there are two

Re: Moving GLib and GTK+ to git

2009-03-31 Thread David Zeuthen
On Tue, 2009-03-31 at 15:58 -0400, Behdad Esfahbod wrote: On 03/31/2009 03:50 PM, David Zeuthen wrote: Personally I prefer non-capital and no periods; it makes the output of 'git log |git shortlog' nicer to look at (see [1] for an example) but maybe that's just me. I think capital letters

Re: Moving GLib and GTK+ to git

2009-03-31 Thread Matthias Clasen
On Tue, Mar 31, 2009 at 3:58 PM, Behdad Esfahbod beh...@behdad.org wrote: On 03/31/2009 03:50 PM, David Zeuthen wrote: Personally I prefer non-capital and no periods; it makes the output of 'git log |git shortlog' nicer to look at (see [1] for an example) but maybe that's just me. I think

Re: Moving GLib and GTK+ to git

2009-03-31 Thread David Zeuthen
On Tue, 2009-03-31 at 17:03 -0400, Matthias Clasen wrote: On Tue, Mar 31, 2009 at 3:58 PM, Behdad Esfahbod beh...@behdad.org wrote: On 03/31/2009 03:50 PM, David Zeuthen wrote: Personally I prefer non-capital and no periods; it makes the output of 'git log |git shortlog' nicer to look at