>> We could just revert that commit (which is only needed for master) and >> re-release soprano 2.9.2, I suppose. And then re-release another >> soprano version with the commit when 4.11 is released. > > > My bad. I shouldn't have put that patch in Soprano 2.9.1. I was hoping to > only have to do the release once for the next six months since I do not see > any other changes that will be required in Soprano for 4.11 > > I think the only possible solution is to release a new Soprano version > (2.9.2?) with the reverted patch. Though maybe KDE/4.10 would be the correct > place to fix this .. hmm.
Yeah, 2.9.2 with the revert sounds good. Thinking about it, any KDE/4.10 fix would be a hack - plus it would have to wait a full month and would only be in use for one minor version, so it doesn't seem worth the effort Simeon _______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
