Skip to Content.
Sympa Menu

sm-commit - Re: [SM-Commit] GIT changes to master grimoire by Ladislav Hagara (ee48e9bcadf87049be62ae010eee3a24904a7438)

sm-commit AT lists.ibiblio.org

Subject: Source Mage code commit list

List archive

Chronological Thread  
  • From: Eric Sandall <eric AT sandall.us>
  • To: "sm-commit AT lists.ibiblio.org" <sm-commit AT lists.ibiblio.org>
  • Subject: Re: [SM-Commit] GIT changes to master grimoire by Ladislav Hagara (ee48e9bcadf87049be62ae010eee3a24904a7438)
  • Date: Wed, 23 Sep 2009 19:27:29 -0700

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ladislav Hagara wrote:
>>> We have this version, but it is the devel version of gtk+2. I don't
>>> think people want to use a devel branch of something as crucial to the
>>> rest of their system as GTK.
>> I see you just replied to SM-Discuss about this. Commits to test are
>> *required* to work, yet this won't. If it's not ready, don't push it to
>> test.
>
> Gtk+2 worked, you just had to choose devel branch, imho no problem in
> test grimoire when we know stable version will be released in several
> hours with only small changes. If users didn't choose devel gtk+2 new
> spells just didn't cast. No problem. With this "broken" commit we had
> gnome 2.28 even before official announcement.

Except now people have a partially upgraded GNOME. Does that cause
problems? Did you test? They also now get failures when they do a
`sorcery system-update` which will make them think something is broken.
This is wrong behaviour.

> I really don't think the better is to create new branch in git
> repository and updates bury there.
> What is new with gcc, xorg?
> How many developers working on them?

Of course it's better, it's still being worked on and incomplete. How
could it be better to put an incomplete solution into test which does
*not work without* manual intervention? That is unacceptable, IMO.

What do gcc or xorg have to do with this?

- -sandalle
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq62REACgkQtYuTaRcbbyY5UwCeKyivVqYl4626rMeD8FlY91P7
pKgAn3A0/tGYjW0NAuo+pwJaZOk/ZyHv
=p2s1
-----END PGP SIGNATURE-----





Archive powered by MHonArc 2.6.24.

Top of Page