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: Ladislav Hagara <ladislav.hagara AT unob.cz>
  • Cc: "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: Thu, 24 Sep 2009 03:26:47 +0200


> > 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.

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?

--
Ladislav Hagara




Archive powered by MHonArc 2.6.24.

Top of Page