Hi all,
Good news: GNOME has been accepted as a mentoring organization for GSoC
2011, woo :-)
If you want to be a mentor, please apply with the following form:
http://www.google-melange.com/gsoc/mentor/request/google/gsoc2011/gnome
Also, it's not too late to add ideas to the wiki page, see Chr
On 03/18/11 13:45, Matthew Barnes wrote:
> "g_log: no, GError: yes" is my rule of thumb.
FWIW, I really like to remove translation from vte. It just doesn't make
sense. Good to have a consensus on this.
behdad
___
desktop-devel-list mailing list
deskt
On Fri, Mar 18, 2011 at 12:45 PM, Matthew Barnes wrote:
> On Fri, 2011-03-18 at 11:06 -0400, Colin Walters wrote:
>> * Should we be translating g_warning / g_error ?
>
> "g_log: no, GError: yes" is my rule of thumb.
Ok, fyi:
checkout/evolution [git master]
$ git grep 'g_\(\(warning\)\|\(error\)\
On Fri, 2011-03-18 at 11:06 -0400, Colin Walters wrote:
> * Should we be translating g_warning / g_error ?
"g_log: no, GError: yes" is my rule of thumb.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/list
On Fri, 2011-03-18 at 11:06 -0400, Colin Walters wrote:
> Hi, I couldn't find discussion about this in a brief web search, and
> obviously post-3.0, but since it came up with a patch I wrote:
>
> * Should we be translating g_warning / g_error ?
No. They're programmer or packaging errors. If an er
Hi, I couldn't find discussion about this in a brief web search, and
obviously post-3.0, but since it came up with a patch I wrote:
* Should we be translating g_warning / g_error ?
At the moment, my random local set of git checkouts weighs heavily against:
$ (for x in *; do (cd $x; echo $x; git
