[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: lorax "treebuilder" branch for F16?

On 08/02/2011 08:08 AM, Will Woods wrote:
> On Mon, 2011-08-01 at 15:22 -0700, John Reiser wrote:

>> So it's a _remote_ branch, not an ordinary branch.
> ...of course it's a remote branch. I can't very well push branches onto
> your local machine for you. Sorry?

At the time I asked "Where is it?", I did two "git pull", a few minutes apart,
received nothing [successfully], and "git branch" showed no "treebuilder".
This was on my local git tree, which I cloned about half a year ago
and have updated somewhat regularly.  After clumens' reply, then I pulled
a third time.  Git downloaded approx. 30 changes [the treebuilder ones],
and "git branch -r" revealed "treebuilder".  Now I see treebuilder; thank you.

> Furthermore, it's moving a lot of gnarly C code that we'd had to
> maintain ourselves for the past 5-10  years (?!) upstream, into dracut.

Deleting gnarly code certainly is good.  Merely moving it "upstream"
might just hand the problems to someone unfamiliar with them,
and jnecessitate more time for over-all improvement.

>      I posted this to anaconda-devel-list because I'm looking for
> technical advice/opinions from anaconda developers. 

I consider it to be a technical fault that F-15 did not announce the
larger RAM requirements for install from DVD until shortly before
final release.  Five months of lead time after a technical change
(the need for larger RAM arose by January when initrds were combined)
produced unintended consequences for users.  Five weeks?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]