From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [72.14.220.156] (helo=fg-out-1718.google.com) by linuxtogo.org with esmtp (Exim 4.68) (envelope-from ) id 1JDSXw-0008Gv-OY for openembedded-devel@lists.openembedded.org; Fri, 11 Jan 2008 23:40:16 +0100 Received: by fg-out-1718.google.com with SMTP id 22so1151334fge.20 for ; Fri, 11 Jan 2008 14:40:02 -0800 (PST) Received: by 10.86.26.11 with SMTP id 11mr3402570fgz.72.1200091202706; Fri, 11 Jan 2008 14:40:02 -0800 (PST) Received: from paul.bn.lan ( [194.79.8.34]) by mx.google.com with ESMTPS id e32sm5407991fke.10.2008.01.11.14.40.01 (version=SSLv3 cipher=OTHER); Fri, 11 Jan 2008 14:40:01 -0800 (PST) Date: Sat, 12 Jan 2008 00:45:53 +0200 From: Paul Sokolovsky X-Mailer: The Bat! (v3.64.01 Christmas Edition) Professional X-Priority: 3 (Normal) Message-ID: <272401109.20080112004553@gmail.com> To: openembedded-devel@lists.openembedded.org, In-Reply-To: <745838583.20080110120841@vanille-media.de> References: <1824361960.20080106235611@gmail.com> <47825896.7030301@kernelconcepts.de> <1133928457.20080108163429@gmail.com> <1199810941.6053.50.camel@localhost.localdomain> <456018236.20080110111917@gmail.com> <745838583.20080110120841@vanille-media.de> MIME-Version: 1.0 Subject: Re: [Angstrom-devel] [RFC] Smallscreen mod for GtkFileChooser X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2008 22:40:17 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Michael, Thursday, January 10, 2008, 1:08:41 PM, you wrote: > Paul Sokolovsky wrote: >> I would >> like to raise the original proposal: to apply my patch, at least to >> Angstrom stable branch. >> Of course, I'd prefer .dev to keep in sync >> too, but if there're concerns that applying such patch would lead to >> false feeling that the issue is solved once and for all, and someone >> plans to work on that soon, .dev can be skipped. Otherwise, it still >> can be applied - we of course can shuffle and swap patches anytime the >> changes are required. > I'm +1 for applying it to both branches. At the end of the day, it > "fixes" the issue in the best way for now. We can always improve > later. Thanks, committed to both! > Regards, > :M: -- Best regards, Paul mailto:pmiscml@gmail.com