Hi.
It would be nice if everyone remembered to update code they've
cut'n'pasted from libegg so we make sure that any improvements there are
available in the next development snapshot. I know the egg-recent code
has had fixes lately at least.
Cheers
Kjartan
Hi all,
after the mail to devel-announce-list@gnome.org regarding missing
MAINTAINERS files (which are really too many), here is the second
chapter of our GNOME cleanup series, heading towards the cleanest GNOME
release ever for 2.14.
While I was working on gnome-terminal, I noticed a
remaining
On Fri, Jan 06, 2006, Kjartan Maraas wrote:
It would be nice if everyone remembered to update code they've
cut'n'pasted from libegg so we make sure that any improvements there are
available in the next development snapshot. I know the egg-recent code
has had fixes lately at least.
I think
On Fri, Jan 06, 2006 at 04:04:42PM +, Bastien Nocera wrote:
I think there's a technical way to force the checkout of libegg in all
CVS modules that use it[1], maybe this could be used to force modules
to always use the latest version of libegg from their branch? This is
similar
Hi,
It looks like there have been no released tarballs of gnome-session for
the 2.13 series. As a result, we are still using gnome-session-2.12.0,
which does NOT have the crash-on-critical-warnings code.
Who can make a gnome-session tarball for us?
Federico
Le vendredi 06 janvier 2006 à 12:13 -0600, Federico Mena Quintero a
écrit :
Hi,
It looks like there have been no released tarballs of gnome-session for
the 2.13 series. As a result, we are still using gnome-session-2.12.0,
which does NOT have the crash-on-critical-warnings code.
Who can
Am Freitag, den 06.01.2006, 13:44 -0200 schrieb Guilherme de S. Pastore:
However, when we came to look at it, it was not only gnome-terminal
that
installed it: in my personal /usr/share/applications-registry, I have
files installed by bug-buddy, epiphany, file-roller, gedit, gimp and
