Re: [Yum-devel] [Patch] Resolver Performance and Correctness

2007-06-07 Thread Tim Lauridsen
seth vidal wrote: On Wed, 2007-06-06 at 10:24 +0300, Panu Matilainen wrote: On Tue, 5 Jun 2007, Jeremy Katz wrote: The other thing that would be nice (and you alluded to below) would be actually splitting into a patch series. As it stands right now, it's a good sized diff and it's

[Yum-devel] [Slightly OT] anaconda - available but NOT upgraded logging

2007-06-07 Thread Charlie Brady
This is an anaconda question, but purely concerning the yum backend, I think. anaconda 10 used to log into upgrade.log all packages which were available but not upgraded. anaconda 11 doesn't, and I miss that behaviour. Would someone mind taking a moment to give me some quick pointers as to

hg and branches (Re: [Yum-devel] [Patch] Resolver Performance and Correctness)

2007-06-07 Thread Charlie Brady
On Thu, 7 Jun 2007, Tim Lauridsen wrote: I have tried bot hg and git, hg seams easier to use at first look, but tools like Cogito[1] makes git easier to use. both ones will be fine with me. What troubles me a little, is the warning Jesse[2] sent about hg. Tim [1] : http://git.or.cz/cogito/

Re: hg and branches (Re: [Yum-devel] [Patch] Resolver Performance and Correctness)

2007-06-07 Thread Jesse Keating
On Thursday 07 June 2007 13:37:04 Charlie Brady wrote: AIUI, hg doesn't really need to elegantly deal with lots of branching. You fork a clone of the repo, then merge patch sets from one to the other as you wish. When you have a central system for managing the source, creating new repos is